← previous blocknext block →recent activity
Analyzing
Block #97,519,482
33 transactions · 25 stateful · 2026-08-20 03:33:11 UTC
Parallelism
79/100
Blocked
56%
Avg conflicts / tx
0.79
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,519,482 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w08w19w011w212w313w214w417w121w424w125w526w627w132w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21d6593f…26e1
0x34b655…2a6f
10 touches
10 conflicts
0x38c47502…1005
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x3e04662b…0da2
0x1b6862…e19c
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
10 conflicts on slot 0x21d6593f38…9526e1
Audit this contract →
← previous block·next block →recent activity