← previous blocknext block →recent activity
Analyzing
Block #97,519,959
36 transactions · 35 stateful · 2026-08-20 03:35:35 UTC
Parallelism
61/100
Blocked
71%
Avg conflicts / tx
2.31
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #97,519,959 · 36 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
1w02w13w06w07w08w19w110w211w212w313w414w515w616w517w718w319w423w124w225w326w432w1135w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ba73d09…ba89
0x34b655…2a6f
12 touches
15 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0xd0ec60a1…d241
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x38c47502…1005
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
15 conflicts on slot 0x1ba73d0943…35ba89
Audit this contract →
← previous block·next block →recent activity