← previous blocknext block →recent activity
Analyzing
Block #106,917,471
31 transactions · 27 stateful · 2026-09-22 02:35:40 UTC
Parallelism
81/100
Blocked
48%
Avg conflicts / tx
0.97
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,917,471 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w111w012w116w017w118w219w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x251ee419…4404
0x34b655…2a6f
12 touches
15 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0x70986451…c6bd
0x34b655…2a6f
12 touches
15 conflicts
0xb937475c…5b4e
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x0f94ee4c…189c
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 0x251ee41913…494404
Audit this contract →
← previous block·next block →recent activity