← previous blocknext block →recent activity
Analyzing
Block #106,952,642
24 transactions · 23 stateful · 2026-09-22 05:32:42 UTC
Parallelism
83/100
Blocked
61%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,952,642 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w26w07w18w29w210w312w013w114w217w018w119w020w121w322w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60b6cf89…9374
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x148c2efc…4410
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x91220b8f…7a06
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x08d53462…97ef
0x34ae4d…3fc5
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 0x60b6cf89e4…a49374
Audit this contract →
← previous block·next block →recent activity