← previous blocknext block →recent activity
Analyzing
Block #97,628,693
25 transactions · 22 stateful · 2026-08-20 12:45:36 UTC
Parallelism
88/100
Blocked
32%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,628,693 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w17w08w19w012w014w117w018w119w120w223w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x01ad188c…9b7f
0x91b81b…6d56
4 touches
1 conflict
0x962f9067…c207
0xb0a788…7777
4 touches
1 conflict
0x843d1c63…21ce
0x91b81b…6d56
4 touches
1 conflict
0x82d396a1…2adb
0x91b81b…6d56
4 touches
1 conflict
0x9dd37003…3b83
0xe1c8b7…3022
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity