← previous blocknext block →recent activity
Analyzing
Block #104,325,767
50 transactions · 43 stateful · 2026-09-13 00:49:30 UTC
Parallelism
66/100
Blocked
67%
Avg conflicts / tx
2.58
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #104,325,767 · 50 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w29w313w215w418w321w323w524w628w633w734w835w936w337w1039w1140w441w547w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
24 touches
66 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x4723c2e4…45fa
0x34b655…2a6f
14 touches
21 conflicts
0xc0a73ae2…2e95
0x34b655…2a6f
10 touches
10 conflicts
0x6df1d50f…8a92
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x2bb0d58d…9dcf
0x34b655…2a6f
8 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
66 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity