← previous blocknext block →recent activity
Analyzing
Block #93,419,825
20 transactions · 17 stateful · 2026-08-05 18:34:32 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,419,825 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w18w29w010w311w412w514w615w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x374825f2…bc35
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x038b9243…553d
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xfe768012…b65e
0x34b655…2a6f
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x04e17b28…d9ef
0x34b655…2a6f
6 touches
3 conflicts
0x04e17b28…d9f0
0x34b655…2a6f
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
10 conflicts on slot 0x374825f25f…77bc35
Audit this contract →
← previous block·next block →recent activity