← previous blocknext block →recent activity
Analyzing
Block #102,406,914
119 transactions · 67 stateful · 2026-09-06 07:14:02 UTC
Parallelism
83/100
Blocked
79%
Avg conflicts / tx
2.24
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #102,406,914 · 119 txs across 20 waves · depth 20
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
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w36w07w111w013w115w217w318w419w523w626w728w458w874w190w992w1193w12101w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
30 touches
105 conflicts
0x00000000…003d
0xa6afd3…d132
18 touches
36 conflicts
0xaad6be10…0801
0x2a68ba…90c5
18 touches
36 conflicts
0xc21def1b…c24d
0xa6afd3…d132
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0002
0xf5b5f7…6d70
10 touches
10 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
105 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity