← previous blocknext block →recent activity
Analyzing
Block #85,928,854
24 transactions · 19 stateful · 2026-07-06 07:09:34 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,928,854 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w08w19w111w213w219w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x9aff966c…53ce
0x34b655…2a6f
8 touches
6 conflicts
0x66c99e67…368e
0x34b655…2a6f
6 touches
3 conflicts
0xe732567d…b65d
0x34b655…2a6f
6 touches
3 conflicts
0xafd867b7…2b2d
0x34b655…2a6f
6 touches
3 conflicts
0xb4c35fcd…43ae
0xa6afd3…d132
6 touches
3 conflicts
0x97d5efed…1aa4
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity