← previous blocknext block →recent activity
Analyzing
Block #97,530,150
36 transactions · 35 stateful · 2026-08-20 04:26:50 UTC
Parallelism
64/100
Blocked
69%
Avg conflicts / tx
1.83
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #97,530,150 · 36 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
1w02w13w24w010w011w112w313w414w415w516w517w618w619w720w821w922w1023w1024w1125w329w130w231w235w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
14 touches
21 conflicts
0xec7d120d…7084
0x34b655…2a6f
12 touches
15 conflicts
0x85054dde…45f1
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xdb95e18e…c738
0x1b6862…e19c
6 touches
3 conflicts
0x1dc86774…166a
0x34b655…2a6f
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
21 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity