← previous blocknext block →recent activity
Analyzing
Block #97,606,012
49 transactions · 44 stateful · 2026-08-20 10:51:02 UTC
Parallelism
65/100
Blocked
77%
Avg conflicts / tx
2.06
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #97,606,012 · 49 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
1w02w13w24w35w47w08w09w110w211w312w113w214w215w520w330w346w1648w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0x01617308…0f8c
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c2
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
36 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity