← previous blocknext block →recent activity
Analyzing
Block #106,419,962
33 transactions · 30 stateful · 2026-09-20 08:50:38 UTC
Parallelism
51/100
Blocked
77%
Avg conflicts / tx
3.91
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,419,962 · 33 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
1w02w13w24w35w19w210w313w216w317w418w419w520w621w722w823w924w1025w1126w1227w1330w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
28 touches
91 conflicts
0x49315fd9…cfe3
0x34b655…2a6f
22 touches
55 conflicts
0x5e1c23e9…4f81
0x34b655…2a6f
20 touches
45 conflicts
0x7462b8f2…6312
0x34b655…2a6f
12 touches
15 conflicts
0x6d955786…1327
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
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
91 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity