← previous blocknext block →recent activity
Analyzing
Block #86,621,459
14 transactions · 13 stateful · 2026-07-09 12:17:05 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,621,459 · 14 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
3w04w15w26w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1a8
0xb1dbf0…c0d3
6 touches
3 conflicts
0x8a35acfb…d1a9
0xb1dbf0…c0d3
6 touches
3 conflicts
0xb07a0849…3b62
0xb1dbf0…c0d3
4 touches
1 conflict
0xee28d8b5…bd37
0x34b655…2a6f
4 touches
1 conflict
0xf628b309…0b8a
0x34b655…2a6f
4 touches
1 conflict
0x143dba04…1b98
0xb1dbf0…c0d3
4 touches
1 conflict
0x1e451306…7993
0xb1dbf0…c0d3
4 touches
1 conflict
0x6a248bdc…3c1b
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
3 conflicts on slot 0x8a35acfbc1…6bd1a8
Audit this contract →
← previous block·next block →recent activity