← previous blocknext block →recent activity
Analyzing
Block #106,953,164
25 transactions · 25 stateful · 2026-09-22 05:35:20 UTC
Parallelism
72/100
Blocked
52%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,953,164 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w09w310w111w418w519w420w521w623w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b8dd4b8…8aa7
0x34b655…2a6f
12 touches
15 conflicts
0x8f18c248…9da5
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0xd4c913d7…343d
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
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
15 conflicts on slot 0x7b8dd4b8d4…cc8aa7
Audit this contract →
← previous block·next block →recent activity