← previous blocknext block →recent activity
Analyzing
Block #106,407,081
19 transactions · 19 stateful · 2026-09-20 07:45:48 UTC
Parallelism
42/100
Blocked
63%
Avg conflicts / tx
2.21
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,407,081 · 19 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w27w39w410w512w113w614w715w816w917w1018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b53436c…2ec3
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0xa72ee581…0d10
0xd32edf…ff58
9 touches
10 conflicts
0xb1927b58…f161
0x34b655…2a6f
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
21 conflicts on slot 0x3b53436c6f…c62ec3
Audit this contract →
← previous block·next block →recent activity