← previous blocknext block →recent activity
Analyzing
Block #106,468,319
26 transactions · 23 stateful · 2026-09-20 12:54:04 UTC
Parallelism
58/100
Blocked
61%
Avg conflicts / tx
2.27
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,468,319 · 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
1w02w13w24w35w410w511w612w513w615w718w719w820w921w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf435f5d7…38fc
0x34b655…2a6f
16 touches
28 conflicts
0x8d664414…3344
0x34b655…2a6f
14 touches
21 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x465d39d6…9fc0
0x34b655…2a6f
8 touches
6 conflicts
0x30ae635d…5e67
0x34b655…2a6f
8 touches
6 conflicts
0xad862891…5d02
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
28 conflicts on slot 0xf435f5d7af…4738fc
Audit this contract →
← previous block·next block →recent activity