← previous blocknext block →recent activity
Analyzing
Block #106,100,762
25 transactions · 24 stateful · 2026-09-19 06:04:09 UTC
Parallelism
64/100
Blocked
63%
Avg conflicts / tx
1.36
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,100,762 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w29w310w416w517w619w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd4e632c…e14c
0x34b655…2a6f
12 touches
15 conflicts
0x3c70ac8d…eaf2
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0x8b41ec8f…c2d7
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x1032f16c…a9b1
0x34b655…2a6f
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
15 conflicts on slot 0xfd4e632c76…e1e14c
Audit this contract →
← previous block·next block →recent activity