← previous blocknext block →recent activity
Analyzing
Block #97,552,801
21 transactions · 20 stateful · 2026-08-20 06:21:15 UTC
Parallelism
71/100
Blocked
55%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,552,801 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w06w27w18w39w312w314w415w116w217w520w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb97c885b…2933
0x34b655…2a6f
8 touches
6 conflicts
0x96ba3f59…db68
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xd4c913d7…3439
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x2f358e74…1022
0x34b655…2a6f
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 0xb97c885bff…112933
Audit this contract →
← previous block·next block →recent activity