← previous blocknext block →recent activity
Analyzing
Block #86,661,199
19 transactions · 18 stateful · 2026-07-09 16:43:51 UTC
Parallelism
79/100
Blocked
28%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,661,199 · 19 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
5w06w18w09w111w217w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e9a70ab…e67c
0x34b655…2a6f
4 touches
1 conflict
0x25cdc19f…7efa
0x34b655…2a6f
4 touches
1 conflict
0x2d7ea048…d78e
0x34b655…2a6f
4 touches
1 conflict
0x3d4584df…ffed
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x485ae99d…f26f
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
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 0x0e9a70abf6…d0e67c
Audit this contract →
← previous block·next block →recent activity