← previous blocknext block →recent activity
Analyzing
Block #97,512,955
24 transactions · 23 stateful · 2026-08-20 03:00:20 UTC
Parallelism
83/100
Blocked
52%
Avg conflicts / tx
0.88
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,512,955 · 24 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
1w02w13w25w07w18w110w011w012w113w114w215w317w218w319w223w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x734a17e8…e50d
0xd32edf…ff58
7 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xa3a9ddd2…0eaf
0x34b655…2a6f
6 touches
3 conflicts
0x35c37635…11a6
0x34b655…2a6f
4 touches
1 conflict
0x3a06aac2…c200
0x34b655…2a6f
4 touches
1 conflict
0x3ec26976…d56c
0x34b655…2a6f
4 touches
1 conflict
0x7b67f6cf…0aab
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity