← previous blocknext block →recent activity
Analyzing
Block #106,413,869
16 transactions · 15 stateful · 2026-09-20 08:19:58 UTC
Parallelism
38/100
Blocked
73%
Avg conflicts / tx
2.25
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,413,869 · 16 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
1w02w13w24w36w37w48w310w511w612w713w814w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d664414…3344
0x34b655…2a6f
14 touches
21 conflicts
0xa36c0167…93b2
0x34b655…2a6f
12 touches
15 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
0x8d47c9a4…f11d
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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
21 conflicts on slot 0x8d664414de…103344
Audit this contract →
← previous block·next block →recent activity