← previous blocknext block →recent activity
Analyzing
Block #97,711,297
39 transactions · 38 stateful · 2026-08-20 19:50:26 UTC
Parallelism
64/100
Blocked
68%
Avg conflicts / tx
2.31
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #97,711,297 · 39 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w010w111w012w113w214w315w417w518w621w425w126w727w228w333w834w936w1137w1238w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x40ac662f…df77
0x34b655…2a6f
12 touches
15 conflicts
0x9db64d13…fb98
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x2ce2d49e…d18a
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity