← previous blocknext block →recent activity
Analyzing
Block #106,924,181
38 transactions · 37 stateful · 2026-09-22 03:09:27 UTC
Parallelism
53/100
Blocked
78%
Avg conflicts / tx
3.11
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #106,924,181 · 38 txs across 18 waves · depth 18
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
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w214w315w416w517w618w719w820w934w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1edffb…323e
0x34b655…2a6f
22 touches
55 conflicts
0xccebf5c5…8758
0x34b655…2a6f
18 touches
36 conflicts
0xf7ae2120…d1d2
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…001d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002d
0x1b6862…e19c
16 touches
28 conflicts
0x1f8a126c…9aa6
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 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
55 conflicts on slot 0xba1edffb42…64323e
Audit this contract →
← previous block·next block →recent activity