← previous blocknext block →recent activity
Analyzing
Block #86,812,127
25 transactions · 22 stateful · 2026-07-10 09:31:43 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
1.48
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,812,127 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w08w19w213w114w315w216w417w518w619w623w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0xb06917e8…6985
0x34b655…2a6f
10 touches
10 conflicts
0x875c3459…2879
0x34b655…2a6f
8 touches
6 conflicts
0x8d888c90…5479
0x34b655…2a6f
8 touches
6 conflicts
0x875c3459…2878
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xa100c256…fb30
0x34b655…2a6f
6 touches
3 conflicts
0xc7a15219…7745
0xa6afd3…d132
6 touches
3 conflicts
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
21 conflicts on slot 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity