← previous blocknext block →recent activity
Analyzing
Block #86,222,073
38 transactions · 26 stateful · 2026-07-07 15:47:02 UTC
Parallelism
84/100
Blocked
58%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,222,073 · 38 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w27w08w111w112w213w114w315w416w534w335w436w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd30f9e74…d404
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0xe6f2ae57…2026
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0000
0x431fed…d150
8 touches
6 conflicts
0x00000000…0002
0x431fed…d150
8 touches
6 conflicts
0x00000000…0003
0x431fed…d150
8 touches
6 conflicts
0x1ccfa324…0b93
0x0a917f…7777
8 touches
6 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
10 conflicts on slot 0xd30f9e74d6…9ed404
Audit this contract →
← previous block·next block →recent activity