← previous blocknext block →recent activity
Analyzing
Block #92,310,140
20 transactions · 18 stateful · 2026-08-01 21:30:44 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,310,140 · 20 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
1w02w13w24w35w06w07w18w29w310w411w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49efff8a…d3a0
0x7b9256…1fb2
10 touches
10 conflicts
0xe1f61186…e2f8
0x754704…b603
10 touches
10 conflicts
0x49efff8a…d39d
0x7b9256…1fb2
10 touches
10 conflicts
0x49efff8a…d39c
0x7b9256…1fb2
10 touches
10 conflicts
0x449fbb55…d2d1
0x7b9256…1fb2
10 touches
10 conflicts
0x449fbb55…d2d0
0x7b9256…1fb2
10 touches
10 conflicts
0x00000000…0006
0x7b9256…1fb2
10 touches
10 conflicts
0x177211e2…1c2d
0x754704…b603
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 0x49efff8a68…8fd3a0
Audit this contract →
← previous block·next block →recent activity