← previous blocknext block →recent activity
Analyzing
Block #106,464,062
34 transactions · 31 stateful · 2026-09-20 12:32:38 UTC
Parallelism
41/100
Blocked
81%
Avg conflicts / tx
3.65
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #106,464,062 · 34 txs across 20 waves · depth 20
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w711w812w914w1018w1219w1328w1429w1531w1732w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1927b58…f161
0x34b655…2a6f
18 touches
36 conflicts
0x79a9715a…1049
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001c
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002c
0x1b6862…e19c
16 touches
28 conflicts
0xba5743c7…21c3
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 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
36 conflicts on slot 0xb1927b5859…36f161
Audit this contract →
← previous block·next block →recent activity