← previous blocknext block →recent activity
Analyzing
Block #106,215,764
22 transactions · 21 stateful · 2026-09-19 15:42:58 UTC
Parallelism
55/100
Blocked
71%
Avg conflicts / tx
1.82
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,215,764 · 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
1w02w13w24w36w47w38w49w510w112w614w715w816w920w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7af7ea3…7d7d
0x34b655…2a6f
14 touches
21 conflicts
0x8de2610c…726a
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xb7af7ea38f…ad7d7d
Audit this contract →
← previous block·next block →recent activity