← previous blocknext block →recent activity
Analyzing
Block #89,708,427
13 transactions · 13 stateful · 2026-07-23 18:56:44 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,708,427 · 13 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
1w02w15w26w311w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x141d1664…b70d
0x065c9d…c394
5 touches
3 conflicts
0xddc22bc2…7f7a
0x754704…b603
4 touches
1 conflict
0x062b2598…4e28
0x43cf54…7777
4 touches
1 conflict
0x0dbf9688…c6cf
0x43cf54…7777
4 touches
1 conflict
0x00000000…0000
0x4b6ce4…7f37
4 touches
1 conflict
0x00000000…0002
0x4b6ce4…7f37
4 touches
1 conflict
0x00000000…0003
0x4b6ce4…7f37
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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
3 conflicts on slot 0x141d166445…c7b70d
Audit this contract →
← previous block·next block →recent activity