← previous blocknext block →recent activity
Analyzing
Block #97,602,886
32 transactions · 30 stateful · 2026-08-20 10:35:11 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,602,886 · 32 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w07w114w215w316w017w120w326w130w231w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80eee557…711d
0x34b655…2a6f
6 touches
3 conflicts
0xcc9d4fca…ecbf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5a6a44e8…e779
0x34b655…2a6f
4 touches
1 conflict
0xbbe07a8b…7d08
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
3 conflicts on slot 0x80eee55732…76711d
Audit this contract →
← previous block·next block →recent activity