← previous blocknext block →recent activity
Analyzing
Block #90,233,769
7 transactions · 7 stateful · 2026-07-25 15:07:23 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,233,769 · 7 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x49433c0a…2a96
0x065c9d…c394
3 touches
1 conflict
0x69c6080a…edcd
0x065c9d…c394
3 touches
1 conflict
0x7fe34681…2874
0x065c9d…c394
2 touches
0 conflicts
0x93b06a30…6de9
0x065c9d…c394
2 touches
0 conflicts
0xbf996573…9a6e
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 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: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity