← previous blocknext block →recent activity
Analyzing
Block #97,685,474
26 transactions · 22 stateful · 2026-08-20 17:39:11 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,685,474 · 26 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
1w03w04w17w08w19w010w011w012w113w215w116w318w124w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41be9e75…9773
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x88b255be…0308
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0xe63a9ab2…a44f
0x34b655…2a6f
4 touches
1 conflict
0xe70f6c1d…2539
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x698bc280…a6d9
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
3 conflicts on slot 0x41be9e7517…b39773
Audit this contract →
← previous block·next block →recent activity