← previous blocknext block →recent activity
Analyzing
Block #106,539,226
42 transactions · 37 stateful · 2026-09-20 18:50:56 UTC
Parallelism
64/100
Blocked
59%
Avg conflicts / tx
1.98
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,539,226 · 42 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w010w111w213w317w026w127w128w229w334w735w836w937w1038w1139w1240w1341w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xdbf974a4…b232
0x34b655…2a6f
12 touches
15 conflicts
0xa2bc9923…3304
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xea2d3331…6e36
0x1b6862…e19c
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity