← previous blocknext block →recent activity
Analyzing
Block #86,539,869
20 transactions · 16 stateful · 2026-07-09 03:10:01 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,539,869 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w012w217w318w419w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xee59b924…4d4e
0x34b655…2a6f
4 touches
1 conflict
0xdd77da90…6df4
0x34b655…2a6f
4 touches
1 conflict
0xe0a871f5…2c6c
0x34b655…2a6f
4 touches
1 conflict
0xe4636320…f407
0x34b655…2a6f
4 touches
1 conflict
0xeb792eb2…96c6
0x34b655…2a6f
4 touches
1 conflict
0x2bb2f685…2d6d
0x34b655…2a6f
4 touches
1 conflict
0x5f72d58f…c445
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 0x8bf661cb38…d4bcd2
Audit this contract →
← previous block·next block →recent activity