Satscribe

History

From detailed tx investigations to high-level block summaries. Dive into personal insights or browse the archive of the community. Discover how others interpret txs and blocks.

  • Block: 641187
    Summarize this in a tweet.
    Scribe

    🚀 Just processed Block #641188!

    • Miner: BTC.com Pool
    • Coinbase Value: 848,158,976 sats
    • Total Transactions: 839
    • Top Fee Transaction: 434,112 sats

    Innovation continues with new OP_RETURN messages carrying data. Onward and upward! 🌟

    7 months ago
  • Block: 641187
    Was the block filled to capacity?
    Scribe

    In assessing whether the latest block, with a height of 641188, was filled to capacity, we can look at its size and the total weight.

    This block has a size of 1,059,532 bytes and a weight of 3,993,091 units. The maximum block size in Bitcoin is 1,000,000 bytes, and the weight limit is 4,000,000 units.

    Since 1,059,532 bytes is under the maximum size limit, this block did not reach capacity in terms of bytes. However, it's quite close in terms of weight—at 3,993,091 units, it is just a bit shy of the total weight limit.

    In conclusion, the block was not completely filled to capacity, as it falls short of the maximum byte limit, even though it approaches the weight limit.

    7 months ago
  • Block: 641187
    Was the block filled to capacity?
    Scribe

    To determine whether the current block (height 641187) was filled to capacity, we can analyze its size and the limit imposed by the Bitcoin protocol.

    The current block has the following characteristics:

    • Size: 1,286,192 bytes
    • Weight: 3,992,915 units

    Bitcoin's block size limit is 1 MB (or 1,000,000 bytes) for traditional transactions, but with the introduction of SegWit (Segregated Witness), the weight limit plays a more crucial role. The maximum block weight limit is 4,000,000 units.

    In this case, the block's weight of 3,992,915 units indicates that it is very close to the weight limit, but not at its maximum. Since the standard maximum size limit is circumvented by the weight of SegWit transactions, what we see is:

    • Current Block Weight: 3,992,915 units (just below the 4,000,000 unit limit)
    • Block Size: 1,286,192 bytes (above 1 MB)

    Although the block is filled relatively efficiently, it is not completely filled to capacity based on the unit weight limit. There is still room before reaching the absolute limit.

    In conclusion, while the block is nearly at capacity in terms of weight, it has not reached the maximum allowable weight or size; hence, it can be considered not fully filled to capacity.

    7 months ago
  • Transaction: 1059136524277a350ec86af38dec7342e83a58dd5eb91af40dde9ec639e64269
    Give me a generic overview.
    Scribe

    Transaction Analysis

    Transaction Type

    • Identified Types:
      • The transaction includes both P2WPKH inputs (3) and a P2PKH input (1).
      • It does not exhibit characteristics of privacy-focused techniques or advanced functionality like CoinJoin or multisig.

    Input/Output Characteristics

    • Inputs vs. Outputs:

      • The transaction features a total of 2 inputs aggregating to 515,921 sats and 2 outputs totaling 515,073 sats.
      • The relative size difference between inputs and outputs indicates that the transaction is not consolidating UTXOs, as the total output is significantly lower than the total input.
    • Unexpected Patterns:

      • There are only minor differences between total input and output values, which suggests low volatility or a standard payment scenario.
      • The output size being slightly less than the input implies a sending scenario where the sender retains a portion in an unspent output or pays a transaction fee.

    Fee Analysis

    • Transaction Fee:
      • The fee of 848 sats, relative to the total input size, indicates that the transaction has a typical fee structure and does not represent an exceptional fee-to-value ratio.

    Anomalies and Patterns

    • The transaction is not categorized among high fee payers, suggesting standard or typical behavior in terms of fee payment practices.
    • The absence of advanced methods like CoinJoin and consolidation behaviors may indicate a non-privacy-focused application, reinforcing typical transactional characteristics.

    Conclusion

    This transaction reflects standard P2WPKH and P2PKH usage with no advanced privacy features and a normal fee range.

    7 months ago
  • Block: 646862
    What's unusual or interesting here?
    Scribe

    Examining the current block (height 646862) offers several interesting insights:

    Increased Coinbase Value

    The miner, Huobi.pool, reported a coinbase value of 654,585,790 satoshis, which is notably high for this block, particularly when compared to its predecessor's value of 650,083,184 satoshis. This increase may indicate a strong miner incentive, potentially due to higher transaction fees or a more favorable difficulty adjustment preceding this block.

    Transaction Fees

    The top transaction fees in this block show a significant uptick, with the highest fee recorded at 319,301 satoshis. This contrasts with the previous block's top fee of 255,486 satoshis, highlighting a growing demand for block space. High fees often reflect network congestion or priority for specific transactions, indicating that users are willing to pay more for faster confirmation times.

    OP_RETURN Usage

    While the use of OP_RETURN in the coinbase transaction is present, it's worth noting that this block contains three transactions with data-carrying OP_RETURN outputs, similar to the previous block. This consistency in OP_RETURN usage suggests ongoing engagement in embedding non-financial data in the blockchain, which can point to increasing applications in areas like identity verification and asset representation.

    Variation in Transaction Types

    The wallet types show a healthy distribution, with a mix of legacy P2PKH, P2SH, and newer SegWit formats (P2WPKH, P2WSH), indicating that users are employing various transaction types as the ecosystem evolves.

    7 months ago