← previous blocknext block →recent activity
Analyzing
Block #106,281,663
22 transactions · 22 stateful · 2026-09-19 21:14:39 UTC
Parallelism
55/100
Blocked
64%
Avg conflicts / tx
1.68
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,281,663 · 22 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
1w02w13w24w35w46w58w09w010w511w613w414w516w617w718w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbb571e4…6829
0x34b655…2a6f
12 touches
15 conflicts
0x59db8e89…3cd9
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0018
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0028
0x1b6862…e19c
10 touches
10 conflicts
0x2ce2d49e…d185
0x1b6862…e19c
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 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 0xdbb571e456…b26829
Audit this contract →
← previous block·next block →recent activity