← previous blocknext block →recent activity
Analyzing
Block #86,904,734
12 transactions · 12 stateful · 2026-07-10 19:51:04 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,904,734 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x367b69ad…33d8
0x34b655…2a6f
6 touches
3 conflicts
0x8dfef5ae…9361
0x34b655…2a6f
6 touches
3 conflicts
0xfa786afc…9dd2
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x367b69ad…33d9
0x34b655…2a6f
4 touches
1 conflict
0x4b3b0587…0912
0x34b655…2a6f
4 touches
1 conflict
0x6ea1896c…e06f
0x34b655…2a6f
4 touches
1 conflict
0x6ea1896c…e070
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 0x367b69ad60…4333d8
Audit this contract →
← previous block·next block →recent activity