← previous blocknext block →recent activity
Analyzing
Block #106,958,269
45 transactions · 44 stateful · 2026-09-22 06:01:02 UTC
Parallelism
64/100
Blocked
75%
Avg conflicts / tx
3.96
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,958,269 · 45 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w710w212w713w818w221w423w526w628w829w930w1031w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x213bd5ec…a3fc
0x34b655…2a6f
22 touches
55 conflicts
0x2e954cbf…5eb0
0x34b655…2a6f
16 touches
28 conflicts
0x3f94ef1b…c8b2
0xd32edf…ff58
15 touches
28 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xba5743c7…21c5
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001e
0x1b6862…e19c
12 touches
15 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 0x213bd5ec68…21a3fc
Audit this contract →
← previous block·next block →recent activity