← previous blocknext block →recent activity
Analyzing
Block #87,284,909
15 transactions · 11 stateful · 2026-07-12 14:12:30 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,284,909 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1a8
0xb1dbf0…c0d3
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x5a310d83…cae0
0x34b655…2a6f
6 touches
3 conflicts
0x7f430e47…4cbd
0xb1dbf0…c0d3
4 touches
1 conflict
0x08547d8c…14ff
0x34b655…2a6f
4 touches
1 conflict
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0x144fddd9…bc2a
0x34b655…2a6f
4 touches
1 conflict
0x333c820d…10c1
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: 0xb1dbf05f…b1c0d3
3 conflicts on slot 0x8a35acfbc1…6bd1a8
Audit this contract →
← previous block·next block →recent activity