← previous blocknext block →recent activity
Analyzing
Block #86,656,352
21 transactions · 17 stateful · 2026-07-09 16:11:28 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,656,352 · 21 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
1w02w15w06w17w28w39w413w414w116w018w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
6 touches
3 conflicts
0xfc48137a…510e
0x34b655…2a6f
6 touches
3 conflicts
0x22e00db9…b886
0x34b655…2a6f
4 touches
1 conflict
0x342f88f5…2a06
0x34b655…2a6f
4 touches
1 conflict
0x38948e75…437a
0x34b655…2a6f
4 touches
1 conflict
0x45877cba…0b50
0x34b655…2a6f
4 touches
1 conflict
0x899723a2…657b
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity