← previous blocknext block →recent activity
Analyzing
Block #92,326,557
15 transactions · 13 stateful · 2026-08-01 22:53:17 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,326,557 · 15 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
2w03w16w07w18w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33b49cd9…986b
0x7b9256…1fb2
6 touches
3 conflicts
0x33b49cd9…986c
0x7b9256…1fb2
6 touches
3 conflicts
0x33b49cd9…986d
0x7b9256…1fb2
6 touches
3 conflicts
0x90f099b4…8dbf
0x7b9256…1fb2
6 touches
3 conflicts
0x90f099b4…8dc0
0x7b9256…1fb2
6 touches
3 conflicts
0x90f099b4…8dc3
0x7b9256…1fb2
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
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 0x33b49cd9d8…d7986b
Audit this contract →
← previous block·next block →recent activity