← previous blocknext block →recent activity
Analyzing
Block #106,801,271
21 transactions · 20 stateful · 2026-09-21 16:50:48 UTC
Parallelism
48/100
Blocked
50%
Avg conflicts / tx
1.57
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,801,271 · 21 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
1w03w04w07w19w211w312w013w414w515w616w718w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e6832ca…0340
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
8 touches
6 conflicts
0x5db64465…c385
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
15 conflicts on slot 0x1e6832ca35…920340
Audit this contract →
← previous block·next block →recent activity