← previous blocknext block →recent activity
Analyzing
Block #92,221,665
18 transactions · 16 stateful · 2026-08-01 14:05:44 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,221,665 · 18 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
6w09w010w111w212w313w414w516w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38fe2630…f3e9
0x7b9256…1fb2
12 touches
15 conflicts
0x915eb02e…5cfe
0x7b9256…1fb2
12 touches
15 conflicts
0x915eb02e…5cfb
0x7b9256…1fb2
12 touches
15 conflicts
0x915eb02e…5cfa
0x7b9256…1fb2
12 touches
15 conflicts
0x177211e2…1c2d
0x754704…b603
12 touches
15 conflicts
0xe1f61186…e2f8
0x754704…b603
12 touches
15 conflicts
0x00000000…0006
0x7b9256…1fb2
12 touches
15 conflicts
0x38fe2630…f3e8
0x7b9256…1fb2
12 touches
15 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
15 conflicts on slot 0x38fe263027…f0f3e9
Audit this contract →
← previous block·next block →recent activity