← previous blocknext block →recent activity
Analyzing
Block #106,426,059
20 transactions · 20 stateful · 2026-09-20 09:21:19 UTC
Parallelism
55/100
Blocked
65%
Avg conflicts / tx
2.05
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,426,059 · 20 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
1w02w13w24w36w28w39w410w411w512w613w714w819w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa35fdc94…25b3
0x34b655…2a6f
16 touches
28 conflicts
0x85ac8cc2…3104
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0xb89c7e78…0bef
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x2c2db8e9…fdc7
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
28 conflicts on slot 0xa35fdc9446…a425b3
Audit this contract →
← previous block·next block →recent activity