← previous blocknext block →recent activity
Analyzing
Block #89,702,906
10 transactions · 9 stateful · 2026-07-23 18:28:53 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,702,906 · 10 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
1w02w14w05w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a59ac51…b3a4
0x065c9d…c394
4 touches
1 conflict
0xe8b6e4c2…e20a
0x188d58…ea8e
4 touches
1 conflict
0xe8b6e4c2…e20c
0x188d58…ea8e
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x690117b9…2820
0x3bd359…433a
4 touches
1 conflict
0x6f845aff…9fc9
0x3bd359…433a
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
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
1 conflict on slot 0x8a59ac51eb…24b3a4
Audit this contract →
← previous block·next block →recent activity