← previous blocknext block →recent activity
Analyzing
Block #97,509,643
33 transactions · 32 stateful · 2026-08-20 02:43:39 UTC
Parallelism
58/100
Blocked
63%
Avg conflicts / tx
2.55
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #97,509,643 · 33 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w07w08w19w210w311w312w413w414w515w616w718w719w821w922w1024w1125w126w1228w231w1332w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x2dcc0868…26bf
0x34b655…2a6f
16 touches
28 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0x0304ed8a…9f25
0x34b655…2a6f
8 touches
6 conflicts
0xb244e6c4…331a
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
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
36 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity