← previous blocknext block →recent activity
Analyzing
Block #89,598,641
15 transactions · 14 stateful · 2026-07-23 08:07:01 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,598,641 · 15 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
1w02w15w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa7013be2…c0a8
0x34b655…2a6f
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x42dd4a90…58fd
0x065c9d…c394
2 touches
0 conflicts
0x43377b24…d89b
0x065c9d…c394
2 touches
0 conflicts
0x881ff399…16ab
0x065c9d…c394
2 touches
0 conflicts
0x8e8029d9…ee34
0x065c9d…c394
2 touches
0 conflicts
0xca1fa322…f594
0x065c9d…c394
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