← previous blocknext block →recent activity
Analyzing
Block #97,523,526
53 transactions · 43 stateful · 2026-08-20 03:53:31 UTC
Parallelism
75/100
Blocked
67%
Avg conflicts / tx
1.36
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #97,523,526 · 53 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
1w03w14w25w36w08w09w111w012w115w016w018w019w120w224w325w430w131w634w136w138w239w740w841w242w243w345w251w1252w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8902ba1f…f4b6
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xee4fe1f7…3ead
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x18865c9d…8ced
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
15 conflicts on slot 0x8902ba1fb5…70f4b6
Audit this contract →
← previous block·next block →recent activity