← previous blocknext block →recent activity
Analyzing
Block #89,872,384
20 transactions · 18 stateful · 2026-07-24 08:43:57 UTC
Parallelism
60/100
Blocked
61%
Avg conflicts / tx
1.85
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #89,872,384 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w511w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe418f48b…9a05
0x065c9d…c394
16 touches
28 conflicts
0x889d5e90…929a
0x2a68ba…90c5
16 touches
28 conflicts
0x4c770fe0…b972
0x3bd359…433a
16 touches
28 conflicts
0x00000000…0000
0x714a26…182d
16 touches
28 conflicts
0x00000000…0001
0x714a26…182d
16 touches
28 conflicts
0x00000000…0003
0x714a26…182d
16 touches
28 conflicts
0xa1087a5c…66c4
0x754704…b603
16 touches
28 conflicts
0xddc22bc2…7f7a
0x754704…b603
16 touches
28 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
28 conflicts on slot 0xe418f48be1…869a05
Audit this contract →
← previous block·next block →recent activity