← previous blocknext block →recent activity
Analyzing
Block #97,557,474
25 transactions · 24 stateful · 2026-08-20 06:45:07 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,557,474 · 25 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
1w05w08w09w110w111w212w316w017w418w124w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x6737ee07…9978
0x34b655…2a6f
4 touches
1 conflict
0x728f999a…832f
0x34b655…2a6f
4 touches
1 conflict
0x779cc2f3…fde1
0x34b655…2a6f
4 touches
1 conflict
0x81501297…c4b7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
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 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity