← previous blocknext block →recent activity
Analyzing
Block #106,215,563
32 transactions · 30 stateful · 2026-09-19 15:41:57 UTC
Parallelism
69/100
Blocked
70%
Avg conflicts / tx
1.53
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,215,563 · 32 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w08w49w211w012w113w014w315w416w517w618w719w820w921w126w131w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6567e227…d139
0x34b655…2a6f
14 touches
21 conflicts
0x6b267bdf…b173
0x34b655…2a6f
10 touches
10 conflicts
0xda7ebedf…c64c
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x580c6fe7…0fe9
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x6567e22782…07d139
Audit this contract →
← previous block·next block →recent activity