← previous blocknext block →recent activity
Analyzing
Block #86,966,486
22 transactions · 22 stateful · 2026-07-11 02:43:42 UTC
Parallelism
68/100
Blocked
32%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,966,486 · 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
6w07w18w211w312w414w515w617w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0xfa667abe…bdfc
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x32f1fe90…5ee3
0x34b655…2a6f
6 touches
3 conflicts
0x769c3710…0cdd
0x34b655…2a6f
6 touches
3 conflicts
0x0ae9d2df…f787
0x34b655…2a6f
6 touches
3 conflicts
0x0ae9d2df…f788
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity