← previous blocknext block →recent activity
Analyzing
Block #97,671,300
34 transactions · 22 stateful · 2026-08-20 16:26:28 UTC
Parallelism
82/100
Blocked
36%
Avg conflicts / tx
0.29
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,671,300 · 34 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
1w02w13w213w019w020w323w125w426w529w132w033w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xa1e6d870…7ae0
0x065c9d…c394
6 touches
3 conflicts
0xa8cad9f3…abc1
0xd32edf…ff58
5 touches
3 conflicts
0x09beabbc…065c
0x188d58…ea8e
4 touches
1 conflict
0x09beabbc…065d
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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
3 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity