← previous blocknext block →recent activity
Analyzing
Block #105,760,631
18 transactions · 17 stateful · 2026-09-18 01:29:50 UTC
Parallelism
39/100
Blocked
65%
Avg conflicts / tx
3.11
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,760,631 · 18 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
1w02w17w08w19w210w311w412w513w614w715w816w917w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0xeb5b61a2…b2bc
0x34b655…2a6f
20 touches
45 conflicts
0x31e0d360…e742
0x34b655…2a6f
12 touches
15 conflicts
0x91bb1de1…d675
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
6 touches
3 conflicts
0x953517cb…cdec
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
55 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity