← previous blocknext block →recent activity
Analyzing
Block #86,669,696
22 transactions · 16 stateful · 2026-07-09 17:40:31 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.64
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,669,696 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w510w617w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x0f2a6e9f…ff3b
0x34b655…2a6f
8 touches
6 conflicts
0x11911005…b679
0x34b655…2a6f
8 touches
6 conflicts
0x24815cb4…c709
0x34b655…2a6f
8 touches
6 conflicts
0x70b87e4d…65d5
0x34b655…2a6f
8 touches
6 conflicts
0x727fbce7…0c80
0x34b655…2a6f
8 touches
6 conflicts
0x025393f0…8bab
0x34b655…2a6f
8 touches
6 conflicts
0xb428493a…2ee5
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity