← previous blocknext block →recent activity
Analyzing
Block #100,858,728
20 transactions · 18 stateful · 2026-08-31 21:05:36 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,858,728 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w09w210w011w112w213w314w416w318w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x6518075e…2b17
0x2a68ba…90c5
8 touches
6 conflicts
0x1c4354ac…072e
0x40c49f…2af0
8 touches
6 conflicts
0xb1856468…e84f
0x34b655…2a6f
6 touches
3 conflicts
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0x3e1e8e54…9c83
0x2a68ba…90c5
4 touches
1 conflict
0x78c305da…2c9a
0x34b655…2a6f
4 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: Coinbase Wrapped BTC (cbBTC)
10 conflicts on slot 0x2b54cadb82…7c4425
Audit this contract →
← previous block·next block →recent activity