← previous blocknext block →recent activity
Analyzing
Block #106,109,315
31 transactions · 29 stateful · 2026-09-19 06:47:11 UTC
Parallelism
71/100
Blocked
72%
Avg conflicts / tx
2.58
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,109,315 · 31 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w615w316w317w422w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0589ff7…032a
0x34b655…2a6f
14 touches
21 conflicts
0x8c56b04c…0a4a
0xd32edf…ff58
13 touches
21 conflicts
0x8f4fb904…204f
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0xba5743c7…21c4
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 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
21 conflicts on slot 0xc0589ff7d6…8f032a
Audit this contract →
← previous block·next block →recent activity