← previous blocknext block →recent activity
Analyzing
Block #106,546,124
31 transactions · 29 stateful · 2026-09-20 19:25:38 UTC
Parallelism
55/100
Blocked
66%
Avg conflicts / tx
2.13
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,546,124 · 31 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w48w516w618w721w222w323w824w925w1026w1127w1228w1330w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a2896a0…2a0a
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xd228e29a…a108
0x34b655…2a6f
16 touches
28 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
12 touches
15 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xdbc6e634…e16a
0x1b6862…e19c
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
36 conflicts on slot 0x2a2896a01b…cc2a0a
Audit this contract →
← previous block·next block →recent activity