← previous blocknext block →recent activity
Analyzing
Block #97,611,816
18 transactions · 17 stateful · 2026-08-20 11:20:41 UTC
Parallelism
89/100
Blocked
12%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,611,816 · 18 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
4w06w18w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x62f2b446…48d5
0x065c9d…c394
4 touches
1 conflict
0x247929d5…e5c4
0x065c9d…c394
3 touches
1 conflict
0x01e7b865…6e70
0x188d58…ea8e
2 touches
0 conflicts
0x503d1554…5f02
0x188d58…ea8e
2 touches
0 conflicts
0x503d1554…5f03
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 0xdfa159d0ee…971576
Audit this contract →
← previous block·next block →recent activity