← previous blocknext block →recent activity
Analyzing
Block #92,062,658
20 transactions · 18 stateful · 2026-08-01 00:46:03 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,062,658 · 20 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
1w05w18w09w010w111w212w313w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x925617fc…d0a6
0x7b9256…1fb2
8 touches
6 conflicts
0xe1f61186…e2f8
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x7b9256…1fb2
8 touches
6 conflicts
0x925617fc…d0a5
0x7b9256…1fb2
8 touches
6 conflicts
0x36ef9b65…26d1
0x7b9256…1fb2
8 touches
6 conflicts
0x36ef9b65…26ce
0x7b9256…1fb2
8 touches
6 conflicts
0x36ef9b65…26cd
0x7b9256…1fb2
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
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 0x925617fc20…7ad0a6
Audit this contract →
← previous block·next block →recent activity