← previous blocknext block →recent activity
Analyzing
Block #106,932,794
33 transactions · 29 stateful · 2026-09-22 03:52:48 UTC
Parallelism
79/100
Blocked
59%
Avg conflicts / tx
1.12
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,932,794 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w012w215w016w117w218w319w424w626w327w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4786839b…c29a
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x79dcc7d9…caaa
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xe317dc39…ad58
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0xd18a8dca…452e
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 0x4786839b71…e2c29a
Audit this contract →
← previous block·next block →recent activity