← previous blocknext block →recent activity
Analyzing
Block #102,220,228
30 transactions · 27 stateful · 2026-09-05 15:28:05 UTC
Parallelism
67/100
Blocked
63%
Avg conflicts / tx
1.7
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #102,220,228 · 30 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
1w02w13w24w35w47w212w514w618w623w724w825w726w928w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x256918f1…c4d0
0x34b655…2a6f
14 touches
21 conflicts
0xdc9deb0a…4285
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0x083a8763…5a7f
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 0x256918f186…59c4d0
Audit this contract →
← previous block·next block →recent activity