← previous blocknext block →recent activity
Analyzing
Block #97,385,819
107 transactions · 89 stateful · 2026-08-19 16:04:08 UTC
Parallelism
76/100
Blocked
80%
Avg conflicts / tx
4.06
Longest chain
26 deep
Execution timeline
did this block parallelize well?
view
block #97,385,819 · 107 txs across 26 waves · depth 26
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
wave w25
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w27w38w431w332w436w537w639w741w851w462w563w577w790w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x103de0…bb55
32 touches
120 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0xbb56619b…1b27
0x34b655…2a6f
22 touches
55 conflicts
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
18 touches
36 conflicts
0x92385428…6941
0x34b655…2a6f
18 touches
36 conflicts
0xc3961304…d676
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…003d
0xa6afd3…d132
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
120 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity