← previous blocknext block →recent activity
Analyzing
Block #97,604,969
21 transactions · 21 stateful · 2026-08-20 10:45:41 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,604,969 · 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
1w04w05w06w17w29w010w311w414w416w517w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc9d4fca…ecbf
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x384e1023…fd10
0x34b655…2a6f
6 touches
3 conflicts
0xe5be4bd0…e382
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x97768660…627e
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd5c98027…9fd9
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
15 conflicts on slot 0xcc9d4fcadb…14ecbf
Audit this contract →
← previous block·next block →recent activity