← previous blocknext block →recent activity
Analyzing
Block #86,909,358
14 transactions · 12 stateful · 2026-07-10 20:22:01 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,909,358 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w29w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7efa41dd…b220
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x9bfadad9…7484
0x34b655…2a6f
4 touches
1 conflict
0xa42e8482…b88f
0x34b655…2a6f
4 touches
1 conflict
0xa7e45018…b59c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x51f838e5…da42
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
1 conflict on slot 0x7efa41dd07…2db220
Audit this contract →
← previous block·next block →recent activity