← previous blocknext block →recent activity
Analyzing
Block #85,220,766
13 transactions · 11 stateful · 2026-07-03 00:32:45 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,220,766 · 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
1w03w05w16w17w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x2f47e4fe…8af1
0x40c49f…2af0
4 touches
1 conflict
0x10c8bf6b…bdb6
0x34b655…2a6f
4 touches
1 conflict
0x4a0db291…8568
0x34b655…2a6f
4 touches
1 conflict
0xf5310ef7…485a
0x40c49f…2af0
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xd98b3c10…67b8
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity