← previous blocknext block →recent activity
Analyzing
Block #106,189,702
26 transactions · 25 stateful · 2026-09-19 13:31:45 UTC
Parallelism
69/100
Blocked
60%
Avg conflicts / tx
1.69
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,189,702 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w011w112w213w315w417w418w519w620w723w324w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95fb9c30…63ad
0x34b655…2a6f
14 touches
21 conflicts
0xd62f3741…b903
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c5
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
21 conflicts on slot 0x95fb9c30f3…8263ad
Audit this contract →
← previous block·next block →recent activity