← previous blocknext block →recent activity
Analyzing
Block #86,925,757
13 transactions · 11 stateful · 2026-07-10 22:11:35 UTC
Parallelism
62/100
Blocked
36%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,925,757 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w17w28w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xa248a5dd…4a69
0x34b655…2a6f
6 touches
3 conflicts
0xa412324b…90aa
0x34b655…2a6f
6 touches
3 conflicts
0xa412324b…90ab
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc2099fec…321d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd1db601b…c70d
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity