← previous blocknext block →recent activity
Analyzing
Block #93,923,548
22 transactions · 16 stateful · 2026-08-07 12:47:18 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,923,548 · 22 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
1w02w03w04w05w16w210w111w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c16527f…628c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x32833fdb…06f7
0x34b655…2a6f
4 touches
1 conflict
0x3c78ca04…432c
0x34b655…2a6f
4 touches
1 conflict
0x45ef9175…5ab2
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7c36395e…ac80
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
3 conflicts on slot 0x5c16527f85…5b628c
Audit this contract →
← previous block·next block →recent activity