← previous blocknext block →recent activity
Analyzing
Block #97,496,117
45 transactions · 40 stateful · 2026-08-20 01:35:37 UTC
Parallelism
73/100
Blocked
60%
Avg conflicts / tx
2.13
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #97,496,117 · 45 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w07w08w110w011w012w013w015w116w017w118w219w221w323w224w326w427w528w629w730w833w135w136w237w238w343w1144w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0x3e1b765a…ae54
0x34b655…2a6f
14 touches
21 conflicts
0x6737ee07…9978
0x34b655…2a6f
10 touches
10 conflicts
0xea1d91a3…b583
0x34b655…2a6f
8 touches
6 conflicts
0x728f999a…832f
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity