← previous blocknext block →recent activity
Analyzing
Block #86,736,856
22 transactions · 20 stateful · 2026-07-10 01:08:55 UTC
Parallelism
73/100
Blocked
35%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,736,856 · 22 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
5w06w17w28w39w010w111w413w516w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x07026927…6922
0x34b655…2a6f
4 touches
1 conflict
0x1082298a…e05e
0x34b655…2a6f
4 touches
1 conflict
0x1082298a…e05f
0x34b655…2a6f
4 touches
1 conflict
0x22baafaa…18ea
0x34b655…2a6f
4 touches
1 conflict
0x356f8a28…5791
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
15 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity