← previous blocknext block →recent activity
Analyzing
Block #90,887,698
13 transactions · 13 stateful · 2026-07-27 22:12:05 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,887,698 · 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
1w02w13w24w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xb5155e8d…db8a
0xa6afd3…d132
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0fffa5c0…a3a9
0xa6afd3…d132
4 touches
1 conflict
0x731f2745…9370
0xa6afd3…d132
4 touches
1 conflict
0x1c796c6b…064e
0x34b655…2a6f
4 touches
1 conflict
0x246db7bc…5a30
0x34b655…2a6f
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: MarginAccount
3 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity