← previous blocknext block →recent activity
Analyzing
Block #97,563,078
70 transactions · 61 stateful · 2026-08-20 07:13:47 UTC
Parallelism
66/100
Blocked
77%
Avg conflicts / tx
3.61
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #97,563,078 · 70 txs across 24 waves · depth 24
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w538w640w845w446w247w369w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
28 touches
91 conflicts
0x482471ad…122f
0x34b655…2a6f
22 touches
55 conflicts
0x889d5e90…929a
0x2a68ba…90c5
16 touches
28 conflicts
0xda1f3e2c…b73d
0x34b655…2a6f
14 touches
21 conflicts
0x0e350896…34d8
0x34b655…2a6f
14 touches
21 conflicts
0xec7d120d…7084
0x34b655…2a6f
14 touches
21 conflicts
0x779cc2f3…fde1
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
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
91 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity