← previous blocknext block →recent activity
Analyzing
Block #106,921,515
34 transactions · 29 stateful · 2026-09-22 02:56:01 UTC
Parallelism
76/100
Blocked
66%
Avg conflicts / tx
1.53
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,921,515 · 34 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w28w39w410w011w112w213w314w317w218w321w423w224w525w626w730w131w333w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x709e44f8…3bc5
0x34b655…2a6f
10 touches
10 conflicts
0xb71b074b…2766
0x34b655…2a6f
10 touches
10 conflicts
0x62dad202…cb74
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x42102e63…8aa9
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
8 touches
6 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 0x709e44f8cc…a33bc5
Audit this contract →
← previous block·next block →recent activity