← previous blocknext block →recent activity
Analyzing
Block #101,304,489
73 transactions · 41 stateful · 2026-09-02 10:28:27 UTC
Parallelism
86/100
Blocked
76%
Avg conflicts / tx
1.6
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #101,304,489 · 73 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w48w09w110w513w614w715w216w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
20 touches
45 conflicts
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xb409e204…89ac
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0xeb5b61a2…b2bc
0x34b655…2a6f
10 touches
10 conflicts
0x460bc9a6…1496
0xd32edf…ff58
7 touches
6 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
45 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity