← previous blocknext block →recent activity
Analyzing
Block #106,932,002
39 transactions · 38 stateful · 2026-09-22 03:48:49 UTC
Parallelism
74/100
Blocked
71%
Avg conflicts / tx
2.26
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,932,002 · 39 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
1w02w13w24w35w46w57w09w110w227w430w636w737w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1ad394c…ae23
0x34b655…2a6f
14 touches
21 conflicts
0x858e40c0…7e30
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
12 touches
15 conflicts
0x70986451…c6bd
0x34b655…2a6f
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 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 0xf1ad394c92…5fae23
Audit this contract →
← previous block·next block →recent activity