← previous blocknext block →recent activity
Analyzing
Block #106,934,460
17 transactions · 16 stateful · 2026-09-22 04:01:11 UTC
Parallelism
53/100
Blocked
75%
Avg conflicts / tx
2.12
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,934,460 · 17 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
1w02w13w24w35w06w17w28w39w410w511w612w715w316w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xccebf5c5…8758
0x34b655…2a6f
16 touches
28 conflicts
0x8d5fc820…1750
0x34b655…2a6f
16 touches
28 conflicts
0x3d4ceda4…84c4
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x4979282b…2936
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
28 conflicts on slot 0xccebf5c5cb…c88758
Audit this contract →
← previous block·next block →recent activity