← previous blocknext block →recent activity
Analyzing
Block #93,361,690
27 transactions · 25 stateful · 2026-08-05 13:42:14 UTC
Parallelism
81/100
Blocked
48%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,361,690 · 27 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
1w02w14w06w07w19w010w111w212w113w215w216w318w119w220w421w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80033ffa…f6d3
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x1a287886…0266
0xa6afd3…d132
6 touches
3 conflicts
0xa558e115…fc88
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x91855e…ac7e
6 touches
3 conflicts
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 0x80033ffaf1…dff6d3
Audit this contract →
← previous block·next block →recent activity