← previous blocknext block →recent activity
Analyzing
Block #106,423,103
30 transactions · 28 stateful · 2026-09-20 09:06:26 UTC
Parallelism
47/100
Blocked
64%
Avg conflicts / tx
4.03
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,423,103 · 30 txs across 16 waves · depth 16
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
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w27w38w412w513w614w717w818w819w920w1021w1122w1223w1324w1425w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b53436c…2ec3
0x34b655…2a6f
28 touches
91 conflicts
0x3ca4707c…cbce
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xaf9e9103…3572
0x34b655…2a6f
10 touches
10 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
8 touches
6 conflicts
0x0505bae8…b4fb
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
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 0x3b53436c6f…c62ec3
Audit this contract →
← previous block·next block →recent activity