← previous blocknext block →recent activity
Analyzing
Block #85,513,820
12 transactions · 9 stateful · 2026-07-04 09:04:24 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,513,820 · 12 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
4w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f405549…5e9c
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xb2a59e5e…bec0
0x34b655…2a6f
4 touches
1 conflict
0xd89a11e6…4cb0
0x34b655…2a6f
3 touches
1 conflict
0x25a9d4a3…b182
0x065c9d…c394
2 touches
0 conflicts
0x27395827…ce10
0x065c9d…c394
2 touches
0 conflicts
0x3d1fca16…d653
0x065c9d…c394
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 0x9f40554930…375e9c
Audit this contract →
← previous block·next block →recent activity