← previous blocknext block →recent activity
Analyzing
Block #97,569,679
27 transactions · 21 stateful · 2026-08-20 07:47:23 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,569,679 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w17w18w210w113w219w324w025w426w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xcf80e177…646c
0x34b655…2a6f
6 touches
3 conflicts
0x8d43ee50…e887
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x7d56b722…b022
0x34b655…2a6f
4 touches
1 conflict
0x8d989c17…e984
0x34b655…2a6f
4 touches
1 conflict
0x99af85c8…6cab
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity