← previous blocknext block →recent activity
Analyzing
Block #97,480,329
25 transactions · 23 stateful · 2026-08-20 00:16:12 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,480,329 · 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
3w05w16w07w08w113w114w215w316w317w219w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6628ce53…1a85
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x1e0cf9b1…e924
0x40c49f…2af0
6 touches
3 conflicts
0x516e9b35…57e7
0x34b655…2a6f
6 touches
3 conflicts
0x8ff85b19…dde0
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x6628ce535b…241a85
Audit this contract →
← previous block·next block →recent activity