← previous blocknext block →recent activity
Analyzing
Block #106,366,786
27 transactions · 25 stateful · 2026-09-20 04:23:01 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,366,786 · 27 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
1w02w13w24w37w08w19w010w114w015w316w117w218w319w420w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85ac8cc2…3104
0x34b655…2a6f
16 touches
28 conflicts
0x000bde1a…e123
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x2c2761c0…476e
0x34b655…2a6f
10 touches
10 conflicts
0xb1927b58…f161
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0xd25997d0…a685
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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
28 conflicts on slot 0x85ac8cc23d…013104
Audit this contract →
← previous block·next block →recent activity