← previous blocknext block →recent activity
Analyzing
Block #85,222,459
13 transactions · 12 stateful · 2026-07-03 00:44:03 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,222,459 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w08w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb89a818…e7c1
0x34b655…2a6f
4 touches
1 conflict
0xf5310ef7…485a
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xd16df6cd…5532
0x40c49f…2af0
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xb5b1684b…b727
0x40c49f…2af0
3 touches
1 conflict
0x93b6535b…9936
0x40c49f…2af0
3 touches
1 conflict
0xb583baad…d81d
0x40c49f…2af0
2 touches
0 conflicts
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 0xcb89a8187c…8fe7c1
Audit this contract →
← previous block·next block →recent activity