← previous blocknext block →recent activity
Analyzing
Block #105,933,221
25 transactions · 20 stateful · 2026-09-18 16:00:48 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,933,221 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w07w08w19w210w312w013w115w316w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a429191…9cda
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x6e0f0724…9951
0xd32edf…ff58
7 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00ce02e7…a8d8
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x3a42919159…6b9cda
Audit this contract →
← previous block·next block →recent activity