← previous blocknext block →recent activity
Analyzing
Block #97,362,987
49 transactions · 46 stateful · 2026-08-19 14:02:15 UTC
Parallelism
61/100
Blocked
78%
Avg conflicts / tx
3.55
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #97,362,987 · 49 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w29w314w520w621w723w727w828w529w632w933w1037w1141w1145w1546w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x45ef9175…5ab2
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xfb31d278…9107
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x4f893478…c649
0x34b655…2a6f
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 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
36 conflicts on slot 0x45ef9175ff…2a5ab2
Audit this contract →
← previous block·next block →recent activity