← previous blocknext block →recent activity
Analyzing
Block #93,490,634
16 transactions · 15 stateful · 2026-08-06 00:30:30 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,490,634 · 16 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
3w04w15w06w18w19w110w211w212w313w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x428b6e5b…8909
0x34b655…2a6f
6 touches
3 conflicts
0xe47f0750…4816
0x851145…3f07
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0xf7640726…19a2
0x2a68ba…90c5
4 touches
1 conflict
0x19795ad6…4a16
0x34b655…2a6f
4 touches
1 conflict
0x785c87ba…a0f1
0x34b655…2a6f
4 touches
1 conflict
0x9ba6ae4a…90cb
0x34b655…2a6f
4 touches
1 conflict
0xa86351b8…2c5a
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 0x428b6e5b99…c18909
Audit this contract →
← previous block·next block →recent activity