← previous blocknext block →recent activity
Analyzing
Block #89,668,513
13 transactions · 13 stateful · 2026-07-23 15:34:50 UTC
Parallelism
85/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,668,513 · 13 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
1w02w13w04w15w06w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67bd1a93…1412
0x065c9d…c394
4 touches
1 conflict
0x1ecee167…9364
0x188d58…ea8e
4 touches
1 conflict
0x1ecee167…9365
0x188d58…ea8e
4 touches
1 conflict
0xe8b6e4c2…e20a
0x188d58…ea8e
4 touches
1 conflict
0xe8b6e4c2…e20c
0x188d58…ea8e
4 touches
1 conflict
0xfbad2c6c…0d32
0x188d58…ea8e
4 touches
1 conflict
0xfbad2c6c…0d33
0x188d58…ea8e
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
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
1 conflict on slot 0x67bd1a93ad…f01412
Audit this contract →
← previous block·next block →recent activity