← previous blocknext block →recent activity
Analyzing
Block #106,923,808
35 transactions · 33 stateful · 2026-09-22 03:07:34 UTC
Parallelism
57/100
Blocked
67%
Avg conflicts / tx
2.09
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,923,808 · 35 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w412w514w515w616w617w718w819w920w1021w1122w1224w1325w1427w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x574628e9…dcc3
0x34b655…2a6f
18 touches
36 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
12 touches
15 conflicts
0x16eed475…62dc
0x34b655…2a6f
12 touches
15 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0x65bd5770…5ecf
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 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
36 conflicts on slot 0x574628e919…e4dcc3
Audit this contract →
← previous block·next block →recent activity