← previous blocknext block →recent activity
Analyzing
Block #89,698,503
10 transactions · 9 stateful · 2026-07-23 18:06:44 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,698,503 · 10 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
1w03w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd35bb5ac…3586
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0x0f5d68b0…9336
0x065c9d…c394
2 touches
0 conflicts
0x33808a0a…66a0
0x065c9d…c394
2 touches
0 conflicts
0x40e81e34…c9c2
0x065c9d…c394
2 touches
0 conflicts
0x93215466…0bc0
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