← previous blocknext block →recent activity
Analyzing
Block #106,381,599
22 transactions · 21 stateful · 2026-09-20 05:37:34 UTC
Parallelism
55/100
Blocked
57%
Avg conflicts / tx
2.45
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,381,599 · 22 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w16w29w310w413w516w617w718w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x4d091c36…3028
0x34b655…2a6f
10 touches
10 conflicts
0x5c8d8e93…e68a
0x34b655…2a6f
10 touches
10 conflicts
0xe8058ec4…ebac
0x34b655…2a6f
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity