← previous blocknext block →recent activity
Analyzing
Block #103,212,682
35 transactions · 32 stateful · 2026-09-09 03:02:00 UTC
Parallelism
66/100
Blocked
63%
Avg conflicts / tx
1.29
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #103,212,682 · 35 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w19w510w611w716w517w620w723w426w331w833w1034w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0x422d5490…52d9
0x34b655…2a6f
10 touches
10 conflicts
0x66799f5f…f85a
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0xd8d828a7…b64b
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity