← previous blocknext block →recent activity
Analyzing
Block #106,235,007
19 transactions · 18 stateful · 2026-09-19 17:19:52 UTC
Parallelism
53/100
Blocked
67%
Avg conflicts / tx
2.05
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,235,007 · 19 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
1w02w13w24w35w48w511w614w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6040987…df02
0x34b655…2a6f
16 touches
28 conflicts
0x8648d74e…0b40
0x34b655…2a6f
10 touches
10 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
6 touches
3 conflicts
0x6a9e408e…3721
0x34b655…2a6f
6 touches
3 conflicts
0x6ee279a7…43b5
0x34b655…2a6f
6 touches
3 conflicts
0x755c7b95…9404
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
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 0xe6040987fc…efdf02
Audit this contract →
← previous block·next block →recent activity