← previous blocknext block →recent activity
Analyzing
Block #106,565,563
40 transactions · 37 stateful · 2026-09-20 21:03:28 UTC
Parallelism
85/100
Blocked
51%
Avg conflicts / tx
1.02
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,565,563 · 40 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w37w08w116w118w223w324w427w131w232w433w434w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6615a36…3cf0
0x34b655…2a6f
12 touches
15 conflicts
0xa6464996…3af9
0x34b655…2a6f
10 touches
10 conflicts
0x4be9812b…48a9
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xe94b93c1…dfa5
0x34b655…2a6f
8 touches
6 conflicts
0xfdb96543…d8a5
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…004c
0x80c745…7210
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
15 conflicts on slot 0xc6615a36ef…7f3cf0
Audit this contract →
← previous block·next block →recent activity