← previous blocknext block →recent activity
Analyzing
Block #92,061,591
11 transactions · 11 stateful · 2026-08-01 00:40:41 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,061,591 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x278b2177…46f5
0x7b9256…1fb2
6 touches
3 conflicts
0x8e5da640…aea7
0x7b9256…1fb2
6 touches
3 conflicts
0x8e5da640…aea8
0x7b9256…1fb2
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x278b2177…46f1
0x7b9256…1fb2
6 touches
3 conflicts
0x278b2177…46f2
0x7b9256…1fb2
6 touches
3 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
3 conflicts on slot 0x278b217733…ef46f5
Audit this contract →
← previous block·next block →recent activity