← previous blocknext block →recent activity
Analyzing
Block #106,566,021
23 transactions · 23 stateful · 2026-09-20 21:05:46 UTC
Parallelism
70/100
Blocked
57%
Avg conflicts / tx
1.61
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,566,021 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w08w011w012w213w014w415w516w117w218w319w420w521w622w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33e472be…0ee1
0x34b655…2a6f
10 touches
10 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
10 touches
10 conflicts
0x41862058…363c
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 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
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
10 conflicts on slot 0x33e472bea8…360ee1
Audit this contract →
← previous block·next block →recent activity