← previous blocknext block →recent activity
Analyzing
Block #86,635,213
18 transactions · 17 stateful · 2026-07-09 13:48:58 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,635,213 · 18 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
1w02w15w06w17w28w310w416w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0xb1dbf0…c0d3
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x2ad3d6b8…f817
0x34b655…2a6f
4 touches
1 conflict
0x3133f94b…f76b
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3d4584df…ffed
0x34b655…2a6f
4 touches
1 conflict
0x4572c9a0…5cf9
0x34b655…2a6f
4 touches
1 conflict
0x55c1a07a…51ea
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 0x0000000000…000004
Audit this contract →
← previous block·next block →recent activity