← previous blocknext block →recent activity
Analyzing
Block #97,385,417
98 transactions · 84 stateful · 2026-08-19 16:01:11 UTC
Parallelism
77/100
Blocked
80%
Avg conflicts / tx
3.64
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #97,385,417 · 98 txs across 23 waves · depth 23
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w612w113w229w230w331w432w533w736w842w1070w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x103de0…bb55
24 touches
66 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
20 touches
45 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
20 touches
45 conflicts
0x889d5e90…929a
0x2a68ba…90c5
18 touches
36 conflicts
0xb7ab4112…e31c
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…002e
0x1b6862…e19c
16 touches
28 conflicts
0xcad937e9…7872
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 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: 0x103de0b5…25bb55
66 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity