← previous blocknext block →recent activity
Analyzing
Block #97,530,801
53 transactions · 43 stateful · 2026-08-20 04:30:06 UTC
Parallelism
75/100
Blocked
65%
Avg conflicts / tx
1.32
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #97,530,801 · 53 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w010w011w113w114w015w116w217w319w022w023w124w125w226w227w328w432w233w337w444w345w551w1252w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85054dde…45f1
0x34b655…2a6f
12 touches
15 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x12070f84…331c
0xa6afd3…d132
6 touches
3 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 0x85054dde2c…8945f1
Audit this contract →
← previous block·next block →recent activity