← previous blocknext block →recent activity
Analyzing
Block #97,544,340
41 transactions · 39 stateful · 2026-08-20 05:38:13 UTC
Parallelism
61/100
Blocked
64%
Avg conflicts / tx
1.85
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #97,544,340 · 41 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w07w011w012w113w214w215w316w317w418w420w521w622w723w427w532w1135w1237w1340w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0xcf80e177…646c
0x34b655…2a6f
8 touches
6 conflicts
0x0304ed8a…9f25
0x34b655…2a6f
8 touches
6 conflicts
0x3e1b765a…ae54
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x103de0…bb55
6 touches
3 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
21 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity