← previous blocknext block →recent activity
Analyzing
Block #102,205,013
24 transactions · 22 stateful · 2026-09-05 14:11:09 UTC
Parallelism
58/100
Blocked
59%
Avg conflicts / tx
1.38
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #102,205,013 · 24 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
1w02w16w28w310w113w414w515w617w718w819w921w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc852b267…9d14
0x34b655…2a6f
10 touches
10 conflicts
0xbbca708a…981e
0x34b655…2a6f
8 touches
6 conflicts
0xb69465c0…ed9d
0xd32edf…ff58
7 touches
6 conflicts
0xba5743c7…21c6
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity