← previous blocknext block →recent activity
Analyzing
Block #106,362,396
25 transactions · 24 stateful · 2026-09-20 04:00:55 UTC
Parallelism
68/100
Blocked
63%
Avg conflicts / tx
1.72
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,362,396 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w211w012w113w216w317w118w319w420w521w622w724w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecc4ac19…b4ac
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…001a
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xf34802b3…9f0f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
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
28 conflicts on slot 0xecc4ac19be…8fb4ac
Audit this contract →
← previous block·next block →recent activity