← previous blocknext block →recent activity
Analyzing
Block #106,468,407
17 transactions · 16 stateful · 2026-09-20 12:54:30 UTC
Parallelism
53/100
Blocked
56%
Avg conflicts / tx
1.76
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,468,407 · 17 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
1w02w13w26w08w19w210w311w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0262e1c6…52e1
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0xe32e848a…851e
0x34b655…2a6f
10 touches
10 conflicts
0xad1d9367…3f9d
0x34b655…2a6f
6 touches
3 conflicts
0xee3abe30…a581
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x2d071de0…c86e
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 0x0262e1c696…e752e1
Audit this contract →
← previous block·next block →recent activity