← previous blocknext block →recent activity
Analyzing
Block #86,222,364
24 transactions · 22 stateful · 2026-07-07 15:48:59 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,222,364 · 24 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
1w02w17w09w010w211w112w214w015w116w217w319w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6f2ae57…2026
0x3bd359…433a
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0x1ccfa324…0b93
0x0a917f…7777
8 touches
6 conflicts
0x00000000…0003
0x431fed…d150
8 touches
6 conflicts
0x00000000…0002
0x431fed…d150
8 touches
6 conflicts
0x00000000…0000
0x431fed…d150
8 touches
6 conflicts
0x44ad89ba…cf83
0x0a917f…7777
8 touches
6 conflicts
0xbcc5ae85…6ba2
0xa6afd3…d132
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: Wrapped MON (WMON)
6 conflicts on slot 0xe6f2ae5723…282026
Audit this contract →
← previous block·next block →recent activity