← previous blocknext block →recent activity
Analyzing
Block #97,466,598
19 transactions · 19 stateful · 2026-08-19 23:06:53 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,466,598 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w28w39w310w411w512w513w114w216w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x5cfec795…7c0e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xb97c885b…2933
0x34b655…2a6f
6 touches
3 conflicts
0x18865c9d…8ced
0xa6afd3…d132
6 touches
3 conflicts
0x22414fbb…1edf
0xa6afd3…d132
6 touches
3 conflicts
0x4a7b2f08…1c3c
0x34b655…2a6f
6 touches
3 conflicts
0x7fd302db…0c73
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 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity