← previous blocknext block →recent activity
Analyzing
Block #106,915,830
38 transactions · 37 stateful · 2026-09-22 02:27:25 UTC
Parallelism
76/100
Blocked
30%
Avg conflicts / tx
0.84
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,915,830 · 38 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w211w012w113w214w315w416w517w623w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85bfd0af…ce96
0x34b655…2a6f
14 touches
21 conflicts
0x08e2f7cd…82ab
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x90fd40a0…9555
0xd32edf…ff58
7 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 0x85bfd0afba…f5ce96
Audit this contract →
← previous block·next block →recent activity