← previous blocknext block →recent activity
Analyzing
Block #85,972,315
31 transactions · 21 stateful · 2026-07-06 11:59:30 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.26
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,972,315 · 31 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
1w02w111w014w221w123w328w029w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xb68e226d…c054
0xa6afd3…d132
4 touches
1 conflict
0xca0f0668…caf3
0xa6afd3…d132
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x06418825…8dd2
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x67bf9e9f…819b
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity