← previous blocknext block →recent activity
Analyzing
Block #97,385,802
88 transactions · 74 stateful · 2026-08-19 16:04:00 UTC
Parallelism
74/100
Blocked
78%
Avg conflicts / tx
3.74
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #97,385,802 · 88 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
2w03w14w25w37w48w510w611w712w813w947w161w264w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
26 touches
78 conflicts
0xc824469a…6425
0x34b655…2a6f
24 touches
66 conflicts
0xec7d120d…7084
0x34b655…2a6f
22 touches
55 conflicts
0x889d5e90…929a
0x2a68ba…90c5
20 touches
45 conflicts
0xcd91995d…15c7
0x34b655…2a6f
20 touches
45 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…003d
0xa6afd3…d132
18 touches
36 conflicts
0x3199a6b2…eb67
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: Perpl
78 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity