← previous blocknext block →recent activity
Analyzing
Block #86,908,780
20 transactions · 15 stateful · 2026-07-10 20:18:09 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,908,780 · 20 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
1w02w05w06w18w19w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x140191c8…1ced
0x34b655…2a6f
6 touches
3 conflicts
0x230ace69…ed93
0x34b655…2a6f
6 touches
3 conflicts
0x230ace69…ed94
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xb8764b84…4a17
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe1a9f808…b867
0x34b655…2a6f
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
3 conflicts on slot 0x140191c870…fd1ced
Audit this contract →
← previous block·next block →recent activity