← previous blocknext block →recent activity
Analyzing
Block #97,657,929
50 transactions · 41 stateful · 2026-08-20 15:17:30 UTC
Parallelism
84/100
Blocked
59%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,657,929 · 50 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w314w415w517w439w640w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x11258774…9892
0x2a68ba…90c5
10 touches
10 conflicts
0x8a0d91a0…2b15
0x34b655…2a6f
10 touches
10 conflicts
0x56fbe7d2…2952
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0x8b41ec8f…c2d7
0x1b6862…e19c
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
10 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity