← previous blocknext block →recent activity
Analyzing
Block #97,519,227
64 transactions · 51 stateful · 2026-08-20 03:31:54 UTC
Parallelism
66/100
Blocked
84%
Avg conflicts / tx
3.58
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #97,519,227 · 64 txs across 22 waves · depth 22
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w520w123w224w326w227w330w639w540w642w645w650w754w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
26 touches
78 conflicts
0xac2a0273…721b
0x34b655…2a6f
22 touches
55 conflicts
0x737acb78…fce8
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…0019
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0029
0x1b6862…e19c
14 touches
21 conflicts
0xd5b10148…e632
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x1ba73d09…ba89
0x34b655…2a6f
14 touches
21 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
78 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity