← previous blocknext block →recent activity
Analyzing
Block #93,236,794
10 transactions · 10 stateful · 2026-08-05 03:14:16 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,236,794 · 10 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
1w02w13w24w35w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64d76184…af55
0x34b655…2a6f
6 touches
3 conflicts
0xcc40b75f…da7f
0x34b655…2a6f
4 touches
1 conflict
0x0e2c8224…e84b
0x34b655…2a6f
4 touches
1 conflict
0x2fd12b6c…02cc
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0x64d7618488…37af55
Audit this contract →
← previous block·next block →recent activity