← previous blocknext block →recent activity
Analyzing
Block #106,949,795
21 transactions · 20 stateful · 2026-09-22 05:18:22 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,949,795 · 21 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
1w02w13w24w25w06w18w09w110w211w015w116w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca1ba9a3…b622
0x34b655…2a6f
12 touches
15 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
8 touches
6 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
8 touches
6 conflicts
0x70986451…c6bd
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xdb95e18e…c73c
0x1b6862…e19c
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 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 0xca1ba9a303…3ab622
Audit this contract →
← previous block·next block →recent activity