← previous blocknext block →recent activity
Analyzing
Block #97,560,353
25 transactions · 20 stateful · 2026-08-20 06:59:50 UTC
Parallelism
88/100
Blocked
30%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,560,353 · 25 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
2w03w04w17w08w19w110w219w020w124w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x728f999a…832f
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x6737ee07…9978
0x34b655…2a6f
4 touches
1 conflict
0x886f7fe6…8b7a
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 0x728f999afb…4e832f
Audit this contract →
← previous block·next block →recent activity