← previous blocknext block →recent activity
Analyzing
Block #93,227,236
20 transactions · 16 stateful · 2026-08-05 02:26:13 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,227,236 · 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
1w06w07w19w110w111w212w013w114w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e4510aa…e367
0x968279…9342
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0x4832fc28…5a83
0x968279…9342
6 touches
3 conflicts
0x4832fc28…5a84
0x968279…9342
6 touches
3 conflicts
0x4832fc28…5a86
0x968279…9342
6 touches
3 conflicts
0x4e4510aa…e361
0x968279…9342
6 touches
3 conflicts
0x4e4510aa…e362
0x968279…9342
6 touches
3 conflicts
0x4e4510aa…e365
0x968279…9342
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: 0x96827978…f09342
3 conflicts on slot 0x4e4510aa31…18e367
Audit this contract →
← previous block·next block →recent activity