← previous blocknext block →recent activity
Analyzing
Block #102,249,270
25 transactions · 21 stateful · 2026-09-05 17:55:18 UTC
Parallelism
60/100
Blocked
57%
Avg conflicts / tx
1.8
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #102,249,270 · 25 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
1w02w13w24w35w47w011w412w513w514w619w721w822w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08399ab6…0057
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0xd5b10148…e638
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
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
21 conflicts on slot 0x08399ab6e2…e00057
Audit this contract →
← previous block·next block →recent activity