← previous blocknext block →recent activity
Analyzing
Block #86,933,612
13 transactions · 10 stateful · 2026-07-10 23:04:03 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,933,612 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a6f5e37…6c3c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x248e43aa…7287
0x34b655…2a6f
4 touches
1 conflict
0x816c7d6d…98ea
0x34b655…2a6f
4 touches
1 conflict
0x816c7d6d…98eb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf4a681b5…20cf
0x34b655…2a6f
4 touches
1 conflict
0x6da0757f…ff0a
0x34b655…2a6f
3 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
1 conflict on slot 0x0a6f5e3795…116c3c
Audit this contract →
← previous block·next block →recent activity