← previous blocknext block →recent activity
Analyzing
Block #93,454,796
20 transactions · 19 stateful · 2026-08-05 21:30:20 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,454,796 · 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
2w03w14w05w16w28w19w010w111w212w313w215w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9036e012…2b4f
0x968279…9342
8 touches
6 conflicts
0x9036e012…2b50
0x968279…9342
8 touches
6 conflicts
0x9036e012…2b53
0x968279…9342
8 touches
6 conflicts
0x9036e012…2b54
0x968279…9342
8 touches
6 conflicts
0x9036e012…2b56
0x968279…9342
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
8 touches
6 conflicts
0x84dd7f18…727d
0x968279…9342
8 touches
6 conflicts
0x521a5982…a82a
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 0x9036e0121a…bd2b4f
Audit this contract →
← previous block·next block →recent activity