← previous blocknext block →recent activity
Analyzing
Block #86,492,224
26 transactions · 23 stateful · 2026-07-08 21:51:54 UTC
Parallelism
77/100
Blocked
48%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,492,224 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w17w08w19w210w313w114w115w216w218w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdba422af…42ec
0x34b655…2a6f
10 touches
10 conflicts
0xf8abc7c4…b16c
0x34b655…2a6f
8 touches
6 conflicts
0x7a03fd7f…3546
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0xf15690fb…74f6
0x34b655…2a6f
6 touches
3 conflicts
0x68e52406…3352
0x34b655…2a6f
4 touches
1 conflict
0x8590b692…b267
0x34b655…2a6f
4 touches
1 conflict
0x9a23a1ec…dc32
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
10 conflicts on slot 0xdba422aff7…3642ec
Audit this contract →
← previous block·next block →recent activity