← previous blocknext block →recent activity
Analyzing
Block #93,455,203
20 transactions · 18 stateful · 2026-08-05 21:32:23 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,455,203 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w07w18w29w310w411w112w518w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabd0bcfc…64e2
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xbdb71f0a…c5c9
0x34b655…2a6f
6 touches
3 conflicts
0x785c87ba…a0f1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x88c6d984…aa1f
0x34b655…2a6f
5 touches
3 conflicts
0xc824469a…6426
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 0xabd0bcfc80…a364e2
Audit this contract →
← previous block·next block →recent activity