← previous blocknext block →recent activity
Analyzing
Block #106,789,958
29 transactions · 25 stateful · 2026-09-21 15:53:50 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
1.24
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,789,958 · 29 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w47w48w514w115w116w220w621w728w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2c61c46…a216
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xcd61c009…9052
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0xc0f29314…17f9
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
10 conflicts on slot 0xe2c61c4697…d2a216
Audit this contract →
← previous block·next block →recent activity