← previous blocknext block →recent activity
Analyzing
Block #92,050,162
16 transactions · 16 stateful · 2026-07-31 23:43:12 UTC
Parallelism
69/100
Blocked
44%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,050,162 · 16 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
2w05w16w07w18w29w310w411w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d298643…e4a3
0x7b9256…1fb2
10 touches
10 conflicts
0x0d298643…e4a4
0x7b9256…1fb2
10 touches
10 conflicts
0x177211e2…1c2d
0x754704…b603
10 touches
10 conflicts
0xe1f61186…e2f8
0x754704…b603
10 touches
10 conflicts
0x00000000…0006
0x7b9256…1fb2
10 touches
10 conflicts
0xa7734fa2…79cb
0x7b9256…1fb2
10 touches
10 conflicts
0xa7734fa2…79c8
0x7b9256…1fb2
10 touches
10 conflicts
0xa7734fa2…79c7
0x7b9256…1fb2
10 touches
10 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: 0x7b9256fd…e21fb2
10 conflicts on slot 0x0d298643a2…bce4a3
Audit this contract →
← previous block·next block →recent activity