← previous blocknext block →recent activity
Analyzing
Block #106,422,254
24 transactions · 23 stateful · 2026-09-20 09:02:10 UTC
Parallelism
38/100
Blocked
70%
Avg conflicts / tx
4.75
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,422,254 · 24 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w28w39w311w412w513w614w715w816w917w1018w1119w1220w1321w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe9d1d23…3de2
0x34b655…2a6f
28 touches
91 conflicts
0x24442cb9…eaa1
0x34b655…2a6f
18 touches
36 conflicts
0xef8ae70c…e193
0x34b655…2a6f
16 touches
28 conflicts
0x9d6847ea…177f
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
8 touches
6 conflicts
0x0ed7cc0b…ee52
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
91 conflicts on slot 0xbe9d1d2362…0d3de2
Audit this contract →
← previous block·next block →recent activity