← previous blocknext block →recent activity
Analyzing
Block #106,224,062
28 transactions · 25 stateful · 2026-09-19 16:24:44 UTC
Parallelism
71/100
Blocked
60%
Avg conflicts / tx
1.39
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,224,062 · 28 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
1w02w13w24w35w46w18w09w112w213w318w323w424w525w626w327w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fb15903…01bf
0x34b655…2a6f
12 touches
15 conflicts
0x81c3a5e0…c7a9
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x17a7f697…dcb8
0x1b6862…e19c
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
15 conflicts on slot 0x6fb1590341…2e01bf
Audit this contract →
← previous block·next block →recent activity