← previous blocknext block →recent activity
Analyzing
Block #105,929,158
33 transactions · 30 stateful · 2026-09-18 15:40:21 UTC
Parallelism
79/100
Blocked
57%
Avg conflicts / tx
1.27
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,929,158 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w26w07w18w210w011w115w017w119w322w323w424w525w629w331w432w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd217a146…59a5
0x34b655…2a6f
10 touches
10 conflicts
0xdb11940a…519b
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xa167b8a0…4323
0x34b655…2a6f
6 touches
3 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
10 conflicts on slot 0xd217a14684…4f59a5
Audit this contract →
← previous block·next block →recent activity