← previous blocknext block →recent activity
Analyzing
Block #97,521,887
25 transactions · 20 stateful · 2026-08-20 03:45:16 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,521,887 · 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
2w07w08w09w010w111w115w117w218w020w121w322w424w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x107f84ba…8b0a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1203ea08…52c3
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x31fe33bd…4e72
0x34b655…2a6f
4 touches
1 conflict
0x331a294a…7f59
0x34b655…2a6f
4 touches
1 conflict
0x3d354ff0…b7c5
0x34b655…2a6f
4 touches
1 conflict
0x61f7bce8…3e84
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 0x107f84bac3…0c8b0a
Audit this contract →
← previous block·next block →recent activity