← previous blocknext block →recent activity
Analyzing
Block #102,220,560
26 transactions · 24 stateful · 2026-09-05 15:29:46 UTC
Parallelism
62/100
Blocked
71%
Avg conflicts / tx
2.08
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #102,220,560 · 26 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
1w02w13w24w35w47w39w510w411w412w517w518w619w720w823w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4b566e4…ff24
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x4799917d…7f29
0xd32edf…ff58
11 touches
15 conflicts
0x20b94f7c…2a9b
0x34b655…2a6f
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xf2e7bb96…1a5a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
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
28 conflicts on slot 0xa4b566e42c…3dff24
Audit this contract →
← previous block·next block →recent activity