← previous blocknext block →recent activity
Analyzing
Block #90,946,971
14 transactions · 13 stateful · 2026-07-28 03:10:15 UTC
Parallelism
86/100
Blocked
15%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,946,971 · 14 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
1w06w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0xbdc80bf7…e947
0x34b655…2a6f
4 touches
1 conflict
0x152e595b…97f4
0x065c9d…c394
2 touches
0 conflicts
0x3fc0f741…4887
0x065c9d…c394
2 touches
0 conflicts
0xaf10c5a2…c4e7
0x065c9d…c394
2 touches
0 conflicts
0xe905a239…d13e
0x065c9d…c394
2 touches
0 conflicts
0xedbc1790…f28d
0x065c9d…c394
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