← previous blocknext block →recent activity
Analyzing
Block #106,380,639
20 transactions · 18 stateful · 2026-09-20 05:32:45 UTC
Parallelism
45/100
Blocked
72%
Avg conflicts / tx
2.9
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,380,639 · 20 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w38w49w510w611w712w813w914w815w916w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1e4ade9…32de
0x34b655…2a6f
16 touches
28 conflicts
0xd2facdba…7a7e
0x34b655…2a6f
12 touches
15 conflicts
0x17bb579f…938c
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0xd996735f…8730
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
28 conflicts on slot 0xb1e4ade94a…d132de
Audit this contract →
← previous block·next block →recent activity