← previous blocknext block →recent activity
Analyzing
Block #97,665,834
16 transactions · 15 stateful · 2026-08-20 15:58:21 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,665,834 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w17w08w19w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02b4abec…397d
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xc0988d33…e5c6
0x34b655…2a6f
4 touches
1 conflict
0xdbb2fff3…b122
0x34b655…2a6f
4 touches
1 conflict
0x9a43fde3…debf
0x34b655…2a6f
2 touches
0 conflicts
0xaf5e9c44…e3fe
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x02b4abec82…9b397d
Audit this contract →
← previous block·next block →recent activity