← previous blocknext block →recent activity
Analyzing
Block #106,342,631
32 transactions · 27 stateful · 2026-09-20 02:21:27 UTC
Parallelism
81/100
Blocked
63%
Avg conflicts / tx
1.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,342,631 · 32 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
1w02w13w24w37w09w111w112w113w214w315w418w119w421w523w524w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdf6ca22…ffec
0x34b655…2a6f
10 touches
10 conflicts
0x9ba10aad…9bc5
0x34b655…2a6f
10 touches
10 conflicts
0x000bde1a…e123
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0xac79a0c7…be10
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xcdf6ca22bd…7cffec
Audit this contract →
← previous block·next block →recent activity