← previous blocknext block →recent activity
Analyzing
Block #106,281,689
22 transactions · 20 stateful · 2026-09-19 21:14:47 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
1.27
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,281,689 · 22 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
5w07w09w010w111w113w214w316w217w318w419w521w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbb571e4…6829
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xfd3f04e7…55f4
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0xe098738f…9bbe
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xdbb571e456…b26829
Audit this contract →
← previous block·next block →recent activity