← previous blocknext block →recent activity
Analyzing
Block #97,510,229
11 transactions · 7 stateful · 2026-08-20 02:46:36 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,510,229 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6a229d6f…d644
0xd32edf…ff58
3 touches
1 conflict
0xc6c3010f…808e
0x065c9d…c394
3 touches
1 conflict
0x164435e9…428d
0x065c9d…c394
2 touches
0 conflicts
0x6b9c2dfb…167a
0x065c9d…c394
2 touches
0 conflicts
0xae071df8…5c61
0x065c9d…c394
2 touches
0 conflicts
0x09beabbc…065c
0x188d58…ea8e
2 touches
0 conflicts
0x09beabbc…065d
0x188d58…ea8e
2 touches
0 conflicts
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: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity