← previous blocknext block →recent activity
Analyzing
Block #86,853,883
21 transactions · 19 stateful · 2026-07-10 14:10:59 UTC
Parallelism
81/100
Blocked
26%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,853,883 · 21 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
1w02w14w05w013w116w017w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x5d863b2f…bd28
0x34b655…2a6f
6 touches
3 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xb0450e57…d414
0x34b655…2a6f
4 touches
1 conflict
0x25ca06ff…70f6
0x34b655…2a6f
2 touches
0 conflicts
0x25cd2f6d…4f2f
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity