← previous blocknext block →recent activity
Analyzing
Block #93,580,458
16 transactions · 16 stateful · 2026-08-06 08:02:02 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,580,458 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w210w311w412w414w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1fe0f027…72b4
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x98212952…9ba6
0x34b655…2a6f
6 touches
3 conflicts
0x0ddfdaf2…9e00
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7a2c83a3…a29a
0x34b655…2a6f
4 touches
1 conflict
0x7aae9795…06ed
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
6 conflicts on slot 0x1fe0f02720…e572b4
Audit this contract →
← previous block·next block →recent activity