← previous blocknext block →recent activity
Analyzing
Block #97,502,160
27 transactions · 24 stateful · 2026-08-20 02:06:01 UTC
Parallelism
85/100
Blocked
42%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,502,160 · 27 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w26w310w011w012w113w115w016w217w318w319w025w126w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x886f7fe6…8b7a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x128486ca…4e98
0xa6afd3…d132
4 touches
1 conflict
0x4d953953…ac1f
0xa6afd3…d132
4 touches
1 conflict
0xce163d4f…b563
0xa6afd3…d132
4 touches
1 conflict
0x0099420d…37b4
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: Kuru Exchange: MarginAccount
6 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity