← previous blocknext block →recent activity
Analyzing
Block #86,563,402
23 transactions · 20 stateful · 2026-07-09 05:47:58 UTC
Parallelism
57/100
Blocked
55%
Avg conflicts / tx
1.22
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,563,402 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w09w110w111w214w315w416w517w618w719w820w921w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xb409e204…89ac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xe6c0e7fb…0058
0x34b655…2a6f
7 touches
6 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0x1a9511e8…6135
0x34b655…2a6f
6 touches
3 conflicts
0x689d5e98…d068
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity