← previous blocknext block →recent activity
Analyzing
Block #106,053,944
26 transactions · 25 stateful · 2026-09-19 02:08:32 UTC
Parallelism
58/100
Blocked
76%
Avg conflicts / tx
2.38
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,053,944 · 26 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w17w28w39w211w514w615w717w225w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13b1cd5c…28bc
0x34b655…2a6f
16 touches
28 conflicts
0x0fc536fb…1aa1
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0xd1480c90…ae07
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
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
28 conflicts on slot 0x13b1cd5c37…a328bc
Audit this contract →
← previous block·next block →recent activity