← previous blocknext block →recent activity
Analyzing
Block #97,515,489
35 transactions · 25 stateful · 2026-08-20 03:13:05 UTC
Parallelism
89/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,515,489 · 35 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
4w05w08w010w011w113w214w315w020w221w126w227w128w029w134w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x52e69143…95ad
0x065c9d…c394
6 touches
3 conflicts
0x091a7571…38d8
0x2b46c0…1669
4 touches
1 conflict
0x213ee207…a151
0x2b46c0…1669
4 touches
1 conflict
0x2f74f175…9285
0x2b46c0…1669
4 touches
1 conflict
0x2f74f175…9288
0x2b46c0…1669
4 touches
1 conflict
0xdde1e1b8…a9da
0x2b46c0…1669
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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