← previous blocknext block →recent activity
Analyzing
Block #90,233,933
9 transactions · 9 stateful · 2026-07-25 15:08:13 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,233,933 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xc57e95ac…942b
0x928dc8…8207
4 touches
1 conflict
0xc57e95ac…942e
0x928dc8…8207
4 touches
1 conflict
0xc57e95ac…942f
0x928dc8…8207
4 touches
1 conflict
0xc7fa82f1…81dc
0x065c9d…c394
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x72f36ab1…c809
0x065c9d…c394
4 touches
1 conflict
0x5311f864…0984
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: MarginAccount
3 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity