← previous blocknext block →recent activity
Analyzing
Block #85,725,830
13 transactions · 11 stateful · 2026-07-05 08:37:40 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,725,830 · 13 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
3w06w17w210w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbffde283…3385
0x34b655…2a6f
4 touches
1 conflict
0xc7ac2c0f…f591
0x34b655…2a6f
4 touches
1 conflict
0xd68e01fc…581c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x81906a8e…9459
0x34b655…2a6f
4 touches
1 conflict
0x881fef27…658a
0x34b655…2a6f
4 touches
1 conflict
0x9fa5ad06…5430
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: Perpl
1 conflict on slot 0xbffde283d8…c63385
Audit this contract →
← previous block·next block →recent activity