← previous blocknext block →recent activity
Analyzing
Block #97,560,064
27 transactions · 21 stateful · 2026-08-20 06:58:21 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,560,064 · 27 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
1w02w14w06w07w110w011w112w113w215w326w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x728f999a…832f
0x34b655…2a6f
8 touches
6 conflicts
0xfdc82463…4b64
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x8b41ec8f…c2d5
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
6 conflicts on slot 0x728f999afb…4e832f
Audit this contract →
← previous block·next block →recent activity