← previous blocknext block →recent activity
Analyzing
Block #106,570,297
33 transactions · 32 stateful · 2026-09-20 21:27:18 UTC
Parallelism
70/100
Blocked
41%
Avg conflicts / tx
1.27
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,570,297 · 33 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
1w02w13w24w35w410w014w515w316w617w718w819w930w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17d42502…4e7b
0x34b655…2a6f
14 touches
21 conflicts
0xcb69a552…4424
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xfac61869…a561
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 0x17d42502ba…4f4e7b
Audit this contract →
← previous block·next block →recent activity