← previous blocknext block →recent activity
Analyzing
Block #97,605,592
24 transactions · 24 stateful · 2026-08-20 10:48:53 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,605,592 · 24 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
2w05w07w18w09w110w215w316w417w218w119w523w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c55e8f5…6fb2
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x88724b87…5e65
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x17f192de…765e
0x34b655…2a6f
4 touches
1 conflict
0x2e5cdd04…22ab
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 0x2c55e8f5eb…7c6fb2
Audit this contract →
← previous block·next block →recent activity