← previous blocknext block →recent activity
Analyzing
Block #86,612,684
19 transactions · 17 stateful · 2026-07-09 11:18:29 UTC
Parallelism
79/100
Blocked
59%
Avg conflicts / tx
0.84
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,612,684 · 19 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
1w02w13w14w25w06w07w28w09w111w312w116w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x679795a0…a28c
0xfa32f9…f3f0
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x99f666e3…b2a2
0x3bd359…433a
6 touches
3 conflicts
0x9194f4a3…10b8
0x754704…b603
6 touches
3 conflicts
0x00000000…0000
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…0001
0xfa32f9…f3f0
6 touches
3 conflicts
0x5f1c9a9d…9bc8
0xd32edf…ff58
5 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: 0xfa32f9ec…fef3f0
3 conflicts on slot 0x679795a019…e8a28c
Audit this contract →
← previous block·next block →recent activity