← previous blocknext block →recent activity
Analyzing
Block #92,856,355
11 transactions · 11 stateful · 2026-08-03 19:19:20 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,856,355 · 11 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
3w04w05w16w27w38w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa6cc13d…62bc
0x968279…9342
8 touches
6 conflicts
0xc9b555eb…25e9
0x968279…9342
8 touches
6 conflicts
0xc9b555eb…25ea
0x968279…9342
8 touches
6 conflicts
0xc9b555eb…25ec
0x968279…9342
8 touches
6 conflicts
0xaa6cc13d…62b8
0x968279…9342
8 touches
6 conflicts
0xaa6cc13d…62bb
0x968279…9342
8 touches
6 conflicts
0xaa6cc13d…62be
0x968279…9342
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: 0x96827978…f09342
6 conflicts on slot 0xaa6cc13db0…be62bc
Audit this contract →
← previous block·next block →recent activity