← previous blocknext block →recent activity
Analyzing
Block #97,614,085
78 transactions · 68 stateful · 2026-08-20 11:32:06 UTC
Parallelism
68/100
Blocked
85%
Avg conflicts / tx
3.36
Longest chain
25 deep
Execution timeline
did this block parallelize well?
view
block #97,614,085 · 78 txs across 25 waves · depth 25
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
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
wave w24
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w69w710w813w429w530w943w950w352w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…0002
0x103de0…bb55
22 touches
55 conflicts
0xfed50340…a9be
0xd32edf…ff58
19 touches
45 conflicts
0x00000000…0012
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…001b
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…002b
0x1b6862…e19c
18 touches
36 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
18 touches
36 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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity