← previous blocknext block →recent activity
Analyzing
Block #106,428,305
39 transactions · 39 stateful · 2026-09-20 09:32:37 UTC
Parallelism
56/100
Blocked
72%
Avg conflicts / tx
3.82
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,428,305 · 39 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
1w02w13w24w35w48w29w313w516w217w621w724w1025w1126w1229w1530w1637w838w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d664414…3344
0x34b655…2a6f
22 touches
55 conflicts
0x7fd19f68…126f
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
12 touches
15 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 0x8d664414de…103344
Audit this contract →
← previous block·next block →recent activity