← previous blocknext block →recent activity
Analyzing
Block #86,222,303
21 transactions · 18 stateful · 2026-07-07 15:48:35 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,222,303 · 21 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
2w05w16w07w18w29w310w411w512w618w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0x431fed…d150
14 touches
21 conflicts
0x00000000…0000
0x431fed…d150
14 touches
21 conflicts
0x00000000…0002
0x431fed…d150
14 touches
21 conflicts
0x44ad89ba…cf83
0x0a917f…7777
14 touches
21 conflicts
0x1ccfa324…0b93
0x0a917f…7777
14 touches
21 conflicts
0xa472d565…9fe4
0x3bd359…433a
14 touches
21 conflicts
0xe6f2ae57…2026
0x3bd359…433a
14 touches
21 conflicts
0x22e0cc1d…ad0d
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
21 conflicts on slot 0x0000000000…000003
Audit this contract →
← previous block·next block →recent activity