← previous blocknext block →recent activity
Analyzing
Block #106,959,304
37 transactions · 34 stateful · 2026-09-22 06:06:14 UTC
Parallelism
70/100
Blocked
65%
Avg conflicts / tx
1.84
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,959,304 · 37 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
1w02w13w24w35w46w512w313w114w116w317w418w319w420w521w624w725w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbc6a437…4655
0x34b655…2a6f
16 touches
28 conflicts
0xd192f4ed…d7ec
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001e
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002e
0x1b6862…e19c
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xea2d3331…6e37
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 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 0xfbc6a43719…e44655
Audit this contract →
← previous block·next block →recent activity