← previous blocknext block →recent activity
Analyzing
Block #106,946,852
30 transactions · 25 stateful · 2026-09-22 05:03:33 UTC
Parallelism
77/100
Blocked
64%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,946,852 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w17w28w19w210w315w419w320w421w526w327w429w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91cd366d…5cea
0x34b655…2a6f
10 touches
10 conflicts
0x5f85717d…ad11
0x34b655…2a6f
10 touches
10 conflicts
0x6cae70fc…9929
0xd32edf…ff58
9 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
8 touches
6 conflicts
0xc824469a…6425
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 0x91cd366db5…175cea
Audit this contract →
← previous block·next block →recent activity