← previous blocknext block →recent activity
Analyzing
Block #93,451,216
29 transactions · 26 stateful · 2026-08-05 21:12:20 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,451,216 · 29 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
1w02w13w24w36w07w18w09w111w012w114w015w116w220w326w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x8d0a477e…8d27
0xd32edf…ff58
7 touches
6 conflicts
0xf28d07b9…4fb2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd02bee08…6299
0x34b655…2a6f
6 touches
3 conflicts
0xbcab7dbe…2825
0x34b655…2a6f
4 touches
1 conflict
0xc601b84f…92e7
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity