← previous blocknext block →recent activity
Analyzing
Block #106,585,808
26 transactions · 25 stateful · 2026-09-20 22:45:22 UTC
Parallelism
69/100
Blocked
48%
Avg conflicts / tx
1.46
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,585,808 · 26 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
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x735a86cd…b64d
0x34b655…2a6f
16 touches
28 conflicts
0x174ec0d3…8d7b
0x34b655…2a6f
12 touches
15 conflicts
0x574628e9…dcc3
0x34b655…2a6f
10 touches
10 conflicts
0x5e2ea201…12de
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xf788c790…e66f
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x3dbf1b9b…c0df
0x34b655…2a6f
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 0x735a86cd19…53b64d
Audit this contract →
← previous block·next block →recent activity