← previous blocknext block →recent activity
Analyzing
Block #106,471,354
34 transactions · 32 stateful · 2026-09-20 13:09:20 UTC
Parallelism
82/100
Blocked
59%
Avg conflicts / tx
1.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,471,354 · 34 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
1w02w13w24w35w46w08w49w010w113w221w122w324w427w228w329w430w532w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c840894…764a
0x34b655…2a6f
12 touches
15 conflicts
0xaa35a811…8c66
0x34b655…2a6f
10 touches
10 conflicts
0x98a63897…c7fa
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c3
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
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 0x1c84089465…17764a
Audit this contract →
← previous block·next block →recent activity