← previous blocknext block →recent activity
Analyzing
Block #97,569,160
19 transactions · 17 stateful · 2026-08-20 07:44:44 UTC
Parallelism
74/100
Blocked
29%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,569,160 · 19 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
2w06w07w19w210w316w017w418w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x516e9b35…57e7
0x34b655…2a6f
10 touches
10 conflicts
0x8d14c548…15e0
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x2dc9d8c4…b93c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x60a536a6…ef7a
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
10 conflicts on slot 0x516e9b35e5…8857e7
Audit this contract →
← previous block·next block →recent activity