← previous blocknext block →recent activity
Analyzing
Block #106,944,393
26 transactions · 22 stateful · 2026-09-22 04:51:11 UTC
Parallelism
58/100
Blocked
59%
Avg conflicts / tx
1.58
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,944,393 · 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
1w02w13w24w35w46w513w614w715w516w817w922w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x560c2fdd…1f72
0x34b655…2a6f
16 touches
28 conflicts
0x91cd366d…5cea
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0x394c3833…b4ac
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
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
28 conflicts on slot 0x560c2fdd18…081f72
Audit this contract →
← previous block·next block →recent activity