← previous blocknext block →recent activity
Analyzing
Block #85,906,749
11 transactions · 9 stateful · 2026-07-06 04:42:21 UTC
Parallelism
64/100
Blocked
44%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,906,749 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w28w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x207cc41e…57c6
0x34b655…2a6f
6 touches
3 conflicts
0xd3414a4a…b17f
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xcce16ef2…a133
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x51cb014f…b9c4
0x34b655…2a6f
2 touches
0 conflicts
0x5e782d17…5317
0x34b655…2a6f
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
3 conflicts on slot 0x207cc41ebf…5057c6
Audit this contract →
← previous block·next block →recent activity