← previous blocknext block →recent activity
Analyzing
Block #89,711,590
14 transactions · 11 stateful · 2026-07-23 19:12:40 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,711,590 · 14 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
1w02w19w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x08e26d57…06c6
0x065c9d…c394
2 touches
0 conflicts
0x20102015…1ad3
0x065c9d…c394
2 touches
0 conflicts
0x6aa687c1…763d
0x065c9d…c394
2 touches
0 conflicts
0x9938d87c…42c2
0x065c9d…c394
2 touches
0 conflicts
0xa74999b7…7ef7
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity