← previous blocknext block →recent activity
Analyzing
Block #97,672,517
46 transactions · 38 stateful · 2026-08-20 16:32:51 UTC
Parallelism
63/100
Blocked
76%
Avg conflicts / tx
1.98
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #97,672,517 · 46 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w19w210w311w312w413w419w220w321w428w230w1232w333w334w439w1343w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2108892…2b33
0x34b655…2a6f
12 touches
15 conflicts
0xc2e8bece…67d9
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x2ed9600d…28f7
0x34b655…2a6f
10 touches
10 conflicts
0x3df3de0d…cd8b
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0xd53220ed…4738
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
15 conflicts on slot 0xc210889289…9e2b33
Audit this contract →
← previous block·next block →recent activity