← previous blocknext block →recent activity
Analyzing
Block #105,849,767
28 transactions · 27 stateful · 2026-09-18 08:59:53 UTC
Parallelism
43/100
Blocked
70%
Avg conflicts / tx
4.21
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #105,849,767 · 28 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w37w19w210w311w412w513w614w715w816w917w1018w1119w1220w1321w1422w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
30 touches
105 conflicts
0x2827ae77…4368
0x34b655…2a6f
20 touches
45 conflicts
0x4c32e6b8…b784
0x34b655…2a6f
18 touches
36 conflicts
0x42522e76…2592
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0x23529e13…6f25
0x34b655…2a6f
12 touches
15 conflicts
0xc10b903d…2f54
0x34b655…2a6f
12 touches
15 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
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
105 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity