← previous blocknext block →recent activity
Analyzing
Block #106,215,303
45 transactions · 40 stateful · 2026-09-19 15:40:39 UTC
Parallelism
62/100
Blocked
63%
Avg conflicts / tx
2.98
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,215,303 · 45 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
1w02w16w07w18w217w318w321w422w525w526w627w729w931w1132w1233w1334w1435w1536w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf00e711b…c539
0x34b655…2a6f
24 touches
66 conflicts
0x62116907…7aa2
0x34b655…2a6f
18 touches
36 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
14 touches
21 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
12 touches
15 conflicts
0xda9919d8…4926
0x34b655…2a6f
12 touches
15 conflicts
0x22891c92…012d
0x34b655…2a6f
10 touches
10 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
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
66 conflicts on slot 0xf00e711b37…00c539
Audit this contract →
← previous block·next block →recent activity