← previous blocknext block →recent activity
Analyzing
Block #103,223,569
18 transactions · 18 stateful · 2026-09-09 03:56:51 UTC
Parallelism
61/100
Blocked
61%
Avg conflicts / tx
1.67
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #103,223,569 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w37w49w010w112w413w514w515w616w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xe2dd47d6…62dd
0x34b655…2a6f
12 touches
15 conflicts
0x7c68d10b…8386
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xf2e7bb96…1a56
0x1b6862…e19c
6 touches
3 conflicts
0x11f2dee3…529f
0x34b655…2a6f
6 touches
3 conflicts
0x43e3decb…be40
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity