← previous blocknext block →recent activity
Analyzing
Block #97,531,921
16 transactions · 11 stateful · 2026-08-20 04:35:44 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,531,921 · 16 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
5w08w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x750ba1df…0200
0x065c9d…c394
4 touches
1 conflict
0xeb189ed1…c26b
0x065c9d…c394
3 touches
1 conflict
0x8635c7bf…2a40
0x065c9d…c394
3 touches
1 conflict
0x7af86c00…2055
0xd32edf…ff58
3 touches
1 conflict
0x01e7b865…6e6e
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e70
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity