← previous blocknext block →recent activity
Analyzing
Block #106,373,388
25 transactions · 25 stateful · 2026-09-20 04:56:15 UTC
Parallelism
32/100
Blocked
68%
Avg conflicts / tx
3.08
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,373,388 · 25 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
1w02w13w24w37w48w59w612w713w815w1017w1218w1319w1421w1624w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad1d9367…3f9d
0x34b655…2a6f
22 touches
55 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
14 touches
21 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0xac0b4a08…faae
0x34b655…2a6f
10 touches
10 conflicts
0x8d47c9a4…f11c
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x1b25f260…c429
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
55 conflicts on slot 0xad1d936705…663f9d
Audit this contract →
← previous block·next block →recent activity