← previous blocknext block →recent activity
Analyzing
Block #97,397,654
20 transactions · 19 stateful · 2026-08-19 17:18:17 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,397,654 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w09w110w211w312w413w114w418w519w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0xaf3a1d52…c2dc
0x34b655…2a6f
4 touches
1 conflict
0xb74116b4…dc4a
0x34b655…2a6f
4 touches
1 conflict
0xc4d3d66a…d7a8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity