← previous blocknext block →recent activity
Analyzing
Block #92,006,959
21 transactions · 18 stateful · 2026-07-31 20:05:55 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,006,959 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w08w010w111w012w113w214w315w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb85de79…3e7c
0x7b9256…1fb2
8 touches
6 conflicts
0xeb85de79…3e7d
0x7b9256…1fb2
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
8 touches
6 conflicts
0xe1f61186…e2f8
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x7b9256…1fb2
8 touches
6 conflicts
0xd121bc24…efd8
0x7b9256…1fb2
8 touches
6 conflicts
0xd121bc24…efd9
0x7b9256…1fb2
8 touches
6 conflicts
0xd121bc24…efdc
0x7b9256…1fb2
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: 0x7b9256fd…e21fb2
6 conflicts on slot 0xeb85de7903…253e7c
Audit this contract →
← previous block·next block →recent activity