← previous blocknext block →recent activity
Analyzing
Block #97,670,980
21 transactions · 20 stateful · 2026-08-20 16:24:49 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,670,980 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w08w19w010w012w013w214w115w216w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb99b689d…9ff1
0x34b655…2a6f
8 touches
6 conflicts
0x994986f6…75c3
0xa6afd3…d132
4 touches
1 conflict
0xeed0c5e8…de19
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0adfec5f…8741
0xa6afd3…d132
4 touches
1 conflict
0x6ed96354…c5dd
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
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
6 conflicts on slot 0xb99b689dbc…c39ff1
Audit this contract →
← previous block·next block →recent activity