← previous blocknext block →recent activity
Analyzing
Block #86,752,396
18 transactions · 16 stateful · 2026-07-10 02:52:52 UTC
Parallelism
78/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,752,396 · 18 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
1w04w16w07w18w211w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x727fbce7…0c80
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xf961e090…b991
0x34b655…2a6f
6 touches
3 conflicts
0xa2dd7133…24d0
0x34b655…2a6f
6 touches
3 conflicts
0xaffb5f5a…c26d
0x34b655…2a6f
6 touches
3 conflicts
0x5cf7c492…23a3
0x34b655…2a6f
4 touches
1 conflict
0x7ced4002…dd55
0x34b655…2a6f
4 touches
1 conflict
0x87b6cc5d…ed4a
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 0x727fbce74b…da0c80
Audit this contract →
← previous block·next block →recent activity