← previous blocknext block →recent activity
Analyzing
Block #106,397,305
50 transactions · 43 stateful · 2026-09-20 06:56:37 UTC
Parallelism
66/100
Blocked
77%
Avg conflicts / tx
3
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,397,305 · 50 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w17w28w29w310w118w323w427w528w631w332w733w634w835w938w1239w1040w1343w1648w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0xbe9d1d23…3de2
0x34b655…2a6f
22 touches
55 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0x1ab9db16…85dc
0x34b655…2a6f
12 touches
15 conflicts
0xf969c564…711b
0x34b655…2a6f
12 touches
15 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0xef8ae70c…e193
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 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
55 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity