← previous blocknext block →recent activity
Analyzing
Block #97,535,702
21 transactions · 20 stateful · 2026-08-20 04:54:46 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,535,702 · 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
1w03w06w07w09w010w111w212w313w114w216w117w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59a84baf…4dfa
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
6 touches
3 conflicts
0xc676d3ac…1cc2
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x6c6f37ba…c206
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
3 conflicts on slot 0x59a84bafcb…c44dfa
Audit this contract →
← previous block·next block →recent activity