← previous blocknext block →recent activity
Analyzing
Block #106,224,479
24 transactions · 22 stateful · 2026-09-19 16:26:50 UTC
Parallelism
58/100
Blocked
55%
Avg conflicts / tx
1.83
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,224,479 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w08w19w210w012w113w214w315w416w517w619w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b0f339b…7a71
0x34b655…2a6f
14 touches
21 conflicts
0x76ed8777…1e5f
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0xc737ce4f…a8d8
0x34b655…2a6f
10 touches
10 conflicts
0x24ed74ea…a3ff
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbf0dd721…6823
0x34b655…2a6f
8 touches
6 conflicts
0xf047c3bd…1b2c
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
21 conflicts on slot 0x9b0f339b85…667a71
Audit this contract →
← previous block·next block →recent activity