← previous blocknext block →recent activity
Analyzing
Block #106,224,066
25 transactions · 21 stateful · 2026-09-19 16:24:45 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
1.68
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,224,066 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w28w210w313w414w516w618w721w722w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fadeba0…ef9e
0x34b655…2a6f
16 touches
28 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
6 touches
3 conflicts
0x581b829b…9578
0x34b655…2a6f
6 touches
3 conflicts
0x932a9590…0b19
0x34b655…2a6f
6 touches
3 conflicts
0xc737ce4f…a8d8
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
28 conflicts on slot 0x0fadeba068…f9ef9e
Audit this contract →
← previous block·next block →recent activity