← previous blocknext block →recent activity
Analyzing
Block #86,828,612
12 transactions · 11 stateful · 2026-07-10 11:22:06 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,828,612 · 12 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x816c7d6d…98eb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x248e43aa…7287
0x34b655…2a6f
4 touches
1 conflict
0x816c7d6d…98ea
0x34b655…2a6f
4 touches
1 conflict
0x9e824dae…c656
0x34b655…2a6f
4 touches
1 conflict
0x8eed7e30…c1ef
0x34b655…2a6f
2 touches
0 conflicts
0xbca4de0c…577c
0x34b655…2a6f
2 touches
0 conflicts
0xf2fa6946…2c6b
0x34b655…2a6f
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
1 conflict on slot 0x816c7d6de3…ac98eb
Audit this contract →
← previous block·next block →recent activity