← previous blocknext block →recent activity
Analyzing
Block #89,739,677
16 transactions · 16 stateful · 2026-07-23 21:34:32 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,739,677 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w011w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x726f3144…764f
0x336ed4…c59c
10 touches
10 conflicts
0x00000000…000b
0x90c374…be45
10 touches
10 conflicts
0x00000000…000a
0x90c374…be45
10 touches
10 conflicts
0xf787d5ff…0033
0x336ed4…c59c
10 touches
10 conflicts
0x74ae383e…8658
0x8d1565…6723
10 touches
10 conflicts
0x72595bc9…7a9f
0x8d1565…6723
10 touches
10 conflicts
0x5e6c1015…bc0d
0x336ed4…c59c
10 touches
10 conflicts
0xe33999aa…8e37
0x8d1565…6723
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: 0x336ed437…cfc59c
10 conflicts on slot 0x726f314455…e3764f
Audit this contract →
← previous block·next block →recent activity