← previous blocknext block →recent activity
Analyzing
Block #100,849,555
24 transactions · 17 stateful · 2026-08-31 20:19:27 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,849,555 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w111w012w113w215w017w220w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0xba836783…e955
0xd32edf…ff58
3 touches
1 conflict
0x284e1a30…b256
0x065c9d…c394
3 touches
1 conflict
0x6505f2e6…03ff
0x065c9d…c394
3 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x5f77d60791…b12c84
Audit this contract →
← previous block·next block →recent activity