← previous blocknext block →recent activity
Analyzing
Block #97,495,288
48 transactions · 42 stateful · 2026-08-20 01:31:27 UTC
Parallelism
73/100
Blocked
57%
Avg conflicts / tx
1.31
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #97,495,288 · 48 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w110w011w112w213w014w015w116w017w218w319w320w421w422w526w627w728w430w831w232w133w334w235w936w1047w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x35c37635…11a6
0x34b655…2a6f
10 touches
10 conflicts
0x8902ba1f…f4b6
0x34b655…2a6f
8 touches
6 conflicts
0x338a2160…8525
0x34b655…2a6f
6 touches
3 conflicts
0x90ed08e8…6574
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x7bab4f62…fb5c
0x065c9d…c394
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity