← previous blocknext block →recent activity
Analyzing
Block #86,222,438
24 transactions · 19 stateful · 2026-07-07 15:49:29 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,222,438 · 24 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
6w07w112w013w114w215w016w117w221w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ccfa324…0b93
0x0a917f…7777
6 touches
3 conflicts
0x44ad89ba…cf83
0x0a917f…7777
6 touches
3 conflicts
0x0600e909…c4f2
0x34b655…2a6f
6 touches
3 conflicts
0x0a6f5e37…6c3c
0x34b655…2a6f
6 touches
3 conflicts
0x1cbb8703…8542
0x34b655…2a6f
6 touches
3 conflicts
0xe4af4c87…9964
0x34b655…2a6f
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0xe6f2ae57…2026
0x3bd359…433a
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: 0x0a917fcc…9d7777
3 conflicts on slot 0x1ccfa32498…500b93
Audit this contract →
← previous block·next block →recent activity