← previous blocknext block →recent activity
Analyzing
Block #86,222,169
23 transactions · 22 stateful · 2026-07-07 15:47:41 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,222,169 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w29w013w214w015w116w217w318w419w321w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x431fed…d150
10 touches
10 conflicts
0x00000000…0003
0x431fed…d150
10 touches
10 conflicts
0x44ad89ba…cf83
0x0a917f…7777
10 touches
10 conflicts
0x1ccfa324…0b93
0x0a917f…7777
10 touches
10 conflicts
0xa472d565…9fe4
0x3bd359…433a
10 touches
10 conflicts
0xe6f2ae57…2026
0x3bd359…433a
10 touches
10 conflicts
0x00000000…0000
0x431fed…d150
10 touches
10 conflicts
0xac2a0273…721b
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: 0x431fedb2…76d150
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity