← previous blocknext block →recent activity
Analyzing
Block #93,346,853
16 transactions · 16 stateful · 2026-08-05 12:27:37 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,346,853 · 16 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
4w06w17w28w311w413w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x0494220d…abf6
0x34b655…2a6f
6 touches
3 conflicts
0x6771eae2…7014
0x34b655…2a6f
6 touches
3 conflicts
0xa279b18d…63bc
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x1b1d7f1f…7ef7
0x34b655…2a6f
5 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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity