← previous blocknext block →recent activity
Analyzing
Block #97,524,969
22 transactions · 17 stateful · 2026-08-20 04:00:46 UTC
Parallelism
77/100
Blocked
41%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,524,969 · 22 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
1w02w05w17w08w19w110w211w314w421w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cfec795…7c0e
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x8902ba1f…f4b6
0x34b655…2a6f
6 touches
3 conflicts
0x66312019…f62e
0xe7cd86…c82d
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xdbd4ac9c…07cc
0x34b655…2a6f
4 touches
1 conflict
0x6237f1a7…2f59
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x47bae1…7568
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 0x5cfec7957f…867c0e
Audit this contract →
← previous block·next block →recent activity