← previous blocknext block →recent activity
Analyzing
Block #89,873,213
13 transactions · 11 stateful · 2026-07-24 08:48:07 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,873,213 · 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
1w05w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x97bd64e2…46ce
0x065c9d…c394
7 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xddc22bc2…7f7a
0x754704…b603
6 touches
3 conflicts
0x392a02b5…0019
0x81a224…7777
6 touches
3 conflicts
0xd06cc746…27e4
0x81a224…7777
6 touches
3 conflicts
0xb0a603a9…b125
0x188d58…ea8e
6 touches
3 conflicts
0x00000000…0000
0x714a26…182d
6 touches
3 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: MarginAccount
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity