← previous blocknext block →recent activity
Analyzing
Block #87,409,748
16 transactions · 16 stateful · 2026-07-13 04:07:22 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,409,748 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w37w48w511w112w213w315w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1a8
0xb1dbf0…c0d3
10 touches
10 conflicts
0x8a35acfb…d1a9
0xb1dbf0…c0d3
10 touches
10 conflicts
0xada6e66d…d096
0x34b655…2a6f
6 touches
3 conflicts
0xc2207d3d…59ce
0x34b655…2a6f
6 touches
3 conflicts
0xf301dafb…8f22
0x34b655…2a6f
4 touches
1 conflict
0xfc366eef…6209
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0178c2de…b37d
0xb1dbf0…c0d3
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: 0xb1dbf05f…b1c0d3
10 conflicts on slot 0x8a35acfbc1…6bd1a8
Audit this contract →
← previous block·next block →recent activity