← previous blocknext block →recent activity
Analyzing
Block #86,959,309
13 transactions · 12 stateful · 2026-07-11 01:55:43 UTC
Parallelism
62/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,959,309 · 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
3w05w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9355efee…7bcd
0x34b655…2a6f
6 touches
3 conflicts
0x4681609f…6493
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xe8706f47…bacf
0x34b655…2a6f
4 touches
1 conflict
0xebeee24a…ed8d
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0001
0x0d73bf…be07
2 touches
0 conflicts
0x00000000…0003
0x0d73bf…be07
2 touches
0 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 0x9355efee55…867bcd
Audit this contract →
← previous block·next block →recent activity