← previous blocknext block →recent activity
Analyzing
Block #106,421,655
17 transactions · 17 stateful · 2026-09-20 08:59:09 UTC
Parallelism
53/100
Blocked
76%
Avg conflicts / tx
1.82
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,421,655 · 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
1w02w13w24w26w37w48w59w510w611w612w714w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d6cdb81…2d28
0x34b655…2a6f
12 touches
15 conflicts
0x39000195…a175
0x34b655…2a6f
10 touches
10 conflicts
0x5e1c23e9…4f81
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xf8480e2a…dff1
0x1b6862…e19c
6 touches
3 conflicts
0x4118bd12…924a
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 0x2d6cdb81df…5d2d28
Audit this contract →
← previous block·next block →recent activity