← previous blocknext block →recent activity
Analyzing
Block #103,213,409
29 transactions · 29 stateful · 2026-09-09 03:05:40 UTC
Parallelism
83/100
Blocked
52%
Avg conflicts / tx
1.21
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #103,213,409 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w49w010w111w112w113w215w320w221w322w424w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x0fecee0f…4ab6
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c2
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0xf38a3927…ad62
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity