← previous blocknext block →recent activity
Analyzing
Block #106,367,116
24 transactions · 23 stateful · 2026-09-20 04:24:41 UTC
Parallelism
54/100
Blocked
61%
Avg conflicts / tx
2.04
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,367,116 · 24 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
1w02w13w24w35w46w37w29w010w412w513w617w718w819w920w1023w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d664414…3344
0x34b655…2a6f
16 touches
28 conflicts
0xfabd84b0…4830
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xee4df517…21ea
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x9ac040c1…8221
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x482471ad…122f
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 0x8d664414de…103344
Audit this contract →
← previous block·next block →recent activity